← previous blocknext block →recent activity
Analyzing
Block #95,637,935
33 transactions · 32 stateful · 2026-08-13 13:02:07 UTC
Parallelism
94/100
Blocked
3%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,637,935 · 33 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
2w027w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd07c7fb6…a7c7
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x892ef2eb…89d8
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0x5554dc07…354b
0x34b655…2a6f
2 touches
0 conflicts
0x5d5a6305…73e9
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 0xd07c7fb65c…72a7c7
Audit this contract →
← previous block·next block →recent activity