← previous blocknext block →recent activity
Analyzing
Block #95,213,181
12 transactions · 12 stateful · 2026-08-12 01:12:06 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,213,181 · 12 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
3w05w17w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf99d2cfb…dcdb
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x1af644dc…0822
0x34b655…2a6f
4 touches
1 conflict
0x7b987499…a00c
0x34b655…2a6f
4 touches
1 conflict
0x90a66fa7…9014
0x34b655…2a6f
4 touches
1 conflict
0x33a24f73…b23a
0x34b655…2a6f
2 touches
0 conflicts
0x7f9061c2…46d8
0x34b655…2a6f
2 touches
0 conflicts
0xb4c34153…866b
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
6 conflicts on slot 0xf99d2cfbd5…94dcdb
Audit this contract →
← previous block·next block →recent activity