← previous blocknext block →recent activity
Analyzing
Block #96,579,638
14 transactions · 12 stateful · 2026-08-16 20:00:26 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,579,638 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w19w110w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x954acd1b…5823
0x34b655…2a6f
6 touches
3 conflicts
0xd459bf7b…92c3
0x34b655…2a6f
6 touches
3 conflicts
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x2d58a69f…6820
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0x954acd1b34…4c5823
Audit this contract →
← previous block·next block →recent activity