← previous blocknext block →recent activity
Analyzing
Block #95,626,202
23 transactions · 21 stateful · 2026-08-13 12:03:06 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,626,202 · 23 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
4w05w16w28w39w010w211w012w113w214w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x869ef6ee…0cb1
0x968279…9342
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x403d1791…6478
0x968279…9342
6 touches
3 conflicts
0x403d1791…6479
0x968279…9342
6 touches
3 conflicts
0x403d1791…647b
0x968279…9342
6 touches
3 conflicts
0x869ef6ee…0caa
0x968279…9342
6 touches
3 conflicts
0x869ef6ee…0cab
0x968279…9342
6 touches
3 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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity