← previous blocknext block →recent activity
Analyzing
Block #95,636,510
18 transactions · 17 stateful · 2026-08-13 12:54:57 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,636,510 · 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
2w03w14w25w37w08w09w111w413w014w117w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
12 touches
15 conflicts
0x2a6ce996…6902
0x34b655…2a6f
6 touches
3 conflicts
0xbbedfd60…0fec
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0xaedc3dd6…3c3b
0x34b655…2a6f
4 touches
1 conflict
0xb7e4c78a…f3f6
0x34b655…2a6f
4 touches
1 conflict
0xbf99cee5…73cd
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