← previous blocknext block →recent activity
Analyzing
Block #96,364,056
6 transactions · 5 stateful · 2026-08-16 01:55:52 UTC
Parallelism
50/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,364,056 · 6 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x046740ca…4065
0x34b655…2a6f
2 touches
0 conflicts
0x046740ca…4066
0x34b655…2a6f
2 touches
0 conflicts
0x1bc9bebb…884b
0x34b655…2a6f
2 touches
0 conflicts
0x2ad2e6d1…e192
0x34b655…2a6f
2 touches
0 conflicts
0x31519d10…f76b
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 0x76c4467df9…89ce28
Audit this contract →
← previous block·next block →recent activity