← previous blocknext block →recent activity
Analyzing
Block #96,533,402
18 transactions · 18 stateful · 2026-08-16 16:07:54 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,533,402 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w07w19w010w111w212w313w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0659a3f…90d9
0x000000…a032
10 touches
10 conflicts
0x00000000…000f
0x78999c…f371
10 touches
10 conflicts
0x34b1e500…7687
0x754704…b603
10 touches
10 conflicts
0x00000000…000b
0x78999c…f371
10 touches
10 conflicts
0x00000000…000b
0x754704…b603
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9538ea90…0536
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
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: 0x00000000…7da032
10 conflicts on slot 0xe0659a3f75…9f90d9
Audit this contract →
← previous block·next block →recent activity