← previous blocknext block →recent activity
Analyzing
Block #94,374,582
19 transactions · 18 stateful · 2026-08-09 02:47:03 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.84
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,374,582 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w37w48w511w112w218w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x62738158…e746
0x34b655…2a6f
6 touches
3 conflicts
0xc335872c…4214
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x88adad52…54b7
0x34b655…2a6f
4 touches
1 conflict
0xa6cb8d47…4f25
0x34b655…2a6f
4 touches
1 conflict
0xaedc3dd6…3c3b
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
10 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity