← previous blocknext block →recent activity
Analyzing
Block #96,026,996
13 transactions · 12 stateful · 2026-08-14 21:40:31 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,026,996 · 13 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
1w02w18w09w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x673e2e56…9f5d
0x34b655…2a6f
4 touches
1 conflict
0x9b2c3a81…406f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x124a2fe8…2ea9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
1 conflict on slot 0x673e2e5652…b99f5d
Audit this contract →
← previous block·next block →recent activity