← previous blocknext block →recent activity
Analyzing
Block #96,826,115
14 transactions · 13 stateful · 2026-08-17 16:40:08 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,826,115 · 14 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
2w05w16w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd08d1657…e444
0x34b655…2a6f
6 touches
3 conflicts
0xf2d8abfb…9cb6
0x34b655…2a6f
6 touches
3 conflicts
0xc4a873f6…7dda
0x34b655…2a6f
4 touches
1 conflict
0xb064a9d2…a1a9
0x34b655…2a6f
4 touches
1 conflict
0x602ed980…5e89
0x34b655…2a6f
4 touches
1 conflict
0x602ed980…5e88
0x34b655…2a6f
4 touches
1 conflict
0x476d8377…e9a8
0x34b655…2a6f
4 touches
1 conflict
0x5de9221b…080f
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 0xd08d1657d0…10e444
Audit this contract →
← previous block·next block →recent activity