← previous blocknext block →recent activity
Analyzing
Block #95,557,792
11 transactions · 9 stateful · 2026-08-13 06:19:01 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,557,792 · 11 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
2w06w17w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7dfe7788…8d9f
0x34b655…2a6f
4 touches
1 conflict
0x114017ca…3c26
0x34b655…2a6f
4 touches
1 conflict
0xe9452241…95a3
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0d2de0f6…e6c6
0x34b655…2a6f
2 touches
0 conflicts
0x1f4b63da…1c6a
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 0x7dfe77881e…028d9f
Audit this contract →
← previous block·next block →recent activity