← previous blocknext block →recent activity
Analyzing
Block #95,160,632
18 transactions · 17 stateful · 2026-08-11 20:47:48 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,160,632 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w17w48w010w111w213w215w317w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
12 touches
15 conflicts
0xa779293b…5e59
0x34b655…2a6f
6 touches
3 conflicts
0x58ae9c0f…d6c8
0x34b655…2a6f
6 touches
3 conflicts
0x10efb0c1…2ddc
0x34b655…2a6f
4 touches
1 conflict
0x1d946063…ba90
0x34b655…2a6f
4 touches
1 conflict
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
4 touches
1 conflict
0x401a563c…0ae7
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: Perpl
15 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity