← previous blocknext block →recent activity
Analyzing
Block #96,212,326
15 transactions · 11 stateful · 2026-08-15 13:12:44 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,212,326 · 15 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
2w03w04w16w27w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05896939…9f49
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0003
0x019883…2a9a
4 touches
1 conflict
0x44ad89ba…cf83
0x0cc9b2…7777
4 touches
1 conflict
0x99a3a7c1…1e2b
0x0cc9b2…7777
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
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 0x0589693985…b59f49
Audit this contract →
← previous block·next block →recent activity