← previous blocknext block →recent activity
Analyzing
Block #98,060,408
10 transactions · 9 stateful · 2026-08-22 01:22:10 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,060,408 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0221091a…da2a
0x34b655…2a6f
2 touches
0 conflicts
0x15ec609d…d4a6
0x34b655…2a6f
2 touches
0 conflicts
0x251812c5…1591
0x34b655…2a6f
2 touches
0 conflicts
0x3836a730…b3a9
0x34b655…2a6f
2 touches
0 conflicts
0x3d7f3b9f…e80b
0x34b655…2a6f
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x40c49f17…d22af0
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity