← previous blocknext block →recent activity
Analyzing
Block #96,482,251
8 transactions · 8 stateful · 2026-08-16 11:50:20 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,482,251 · 8 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
1w02w14w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe48fd442…b238
0x968279…9342
4 touches
1 conflict
0xe48fd442…b232
0x968279…9342
4 touches
1 conflict
0xe48fd442…b235
0x968279…9342
4 touches
1 conflict
0xe48fd442…b236
0x968279…9342
4 touches
1 conflict
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xa87df083…3166
0x34b655…2a6f
4 touches
1 conflict
0xb416438e…796a
0x34b655…2a6f
4 touches
1 conflict
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: 0x96827978…f09342
1 conflict on slot 0xe48fd442b6…6db238
Audit this contract →
← previous block·next block →recent activity