← previous blocknext block →recent activity
Analyzing
Block #95,397,631
12 transactions · 12 stateful · 2026-08-12 16:52:39 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,397,631 · 12 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
2w03w14w05w06w17w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f83b9b5…f807
0x968279…9342
4 touches
1 conflict
0x6f83b9b5…f801
0x968279…9342
4 touches
1 conflict
0x6f83b9b5…f804
0x968279…9342
4 touches
1 conflict
0x6f83b9b5…f805
0x968279…9342
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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: 0x96827978…f09342
1 conflict on slot 0x6f83b9b517…0cf807
Audit this contract →
← previous block·next block →recent activity