← previous blocknext block →recent activity
Analyzing
Block #95,727,045
16 transactions · 16 stateful · 2026-08-13 20:31:23 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,727,045 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w312w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31d88d27…7617
0x34b655…2a6f
6 touches
3 conflicts
0x6939e474…4256
0x34b655…2a6f
6 touches
3 conflicts
0x4abfb389…18f4
0x34b655…2a6f
6 touches
3 conflicts
0x8f63f383…6eda
0x34b655…2a6f
6 touches
3 conflicts
0x5484fc7f…a8d8
0x34b655…2a6f
4 touches
1 conflict
0x5559c2e5…928e
0x34b655…2a6f
4 touches
1 conflict
0x57bfec6f…be4b
0x34b655…2a6f
4 touches
1 conflict
0x749a4cb2…15f8
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 0x31d88d27c1…837617
Audit this contract →
← previous block·next block →recent activity