← previous blocknext block →recent activity
Analyzing
Block #96,838,445
16 transactions · 14 stateful · 2026-08-17 17:42:09 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,838,445 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w09w110w212w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2b035ef…4746
0x34b655…2a6f
6 touches
3 conflicts
0xb5a47a02…d364
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x63e367c9…b363
0x754704…b603
4 touches
1 conflict
0xce62e150…1e09
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3f4f9f22…8ad7
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: Perpl
3 conflicts on slot 0xf2b035efb1…6f4746
Audit this contract →
← previous block·next block →recent activity