← previous blocknext block →recent activity
Analyzing
Block #95,710,827
11 transactions · 11 stateful · 2026-08-13 19:09:38 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,710,827 · 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
3w04w05w17w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xedc13a6d…53bc
0x968279…9342
4 touches
1 conflict
0xce3bffa7…360b
0x968279…9342
4 touches
1 conflict
0xedc13a6d…53b5
0x968279…9342
4 touches
1 conflict
0xedc13a6d…53b6
0x968279…9342
4 touches
1 conflict
0xedc13a6d…53b9
0x968279…9342
4 touches
1 conflict
0xedc13a6d…53ba
0x968279…9342
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity