← previous blocknext block →recent activity
Analyzing
Block #96,785,056
11 transactions · 9 stateful · 2026-08-17 13:13:37 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,785,056 · 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
1w02w14w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da59c2b…d7b2
0x34b655…2a6f
4 touches
1 conflict
0x7527177c…0520
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xd09e5313…2b63
0x34b655…2a6f
4 touches
1 conflict
0xf58ef399…86dc
0x34b655…2a6f
4 touches
1 conflict
0x620b761c…270e
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 0x5da59c2b2f…b6d7b2
Audit this contract →
← previous block·next block →recent activity