← previous blocknext block →recent activity
Analyzing
Block #96,640,014
9 transactions · 8 stateful · 2026-08-17 01:04:07 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,640,014 · 9 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
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff196840…a453
0x34b655…2a6f
6 touches
3 conflicts
0x7b1cdad7…9b49
0x34b655…2a6f
4 touches
1 conflict
0x48532ab5…d4c1
0x34b655…2a6f
4 touches
1 conflict
0x48532ab5…d4c2
0x34b655…2a6f
4 touches
1 conflict
0x8702a009…24b2
0x34b655…2a6f
4 touches
1 conflict
0x979d8133…de18
0x34b655…2a6f
4 touches
1 conflict
0xc53799eb…d928
0x34b655…2a6f
4 touches
1 conflict
0xe3c082c7…f032
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 0xff19684070…f2a453
Audit this contract →
← previous block·next block →recent activity