← previous blocknext block →recent activity
Analyzing
Block #95,405,595
14 transactions · 13 stateful · 2026-08-12 17:32:57 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,405,595 · 14 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
1w02w14w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6254804c…a03c
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x3cb4b659…f735
0x34b655…2a6f
2 touches
0 conflicts
0x8b501dcf…1040
0x34b655…2a6f
2 touches
0 conflicts
0xa5904747…afe9
0x34b655…2a6f
2 touches
0 conflicts
0xa9a49465…0424
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 0x6254804ca4…efa03c
Audit this contract →
← previous block·next block →recent activity