← previous blocknext block →recent activity
Analyzing
Block #96,609,696
11 transactions · 10 stateful · 2026-08-16 22:31:38 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,609,696 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44a35e35…6dcf
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc82f66db…833d
0x34b655…2a6f
4 touches
1 conflict
0x0c612d13…2829
0x34b655…2a6f
4 touches
1 conflict
0x27f0e3c6…f709
0x34b655…2a6f
4 touches
1 conflict
0x3226e3fe…f799
0x34b655…2a6f
2 touches
0 conflicts
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 0x44a35e358c…376dcf
Audit this contract →
← previous block·next block →recent activity