← previous blocknext block →recent activity
Analyzing
Block #94,796,513
24 transactions · 22 stateful · 2026-08-10 14:15:27 UTC
Parallelism
75/100
Blocked
64%
Avg conflicts / tx
1.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,796,513 · 24 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
1w02w03w14w25w36w07w18w19w210w211w312w413w118w523w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310afe2c…83e1
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x306830bb…5d2d
0xd32edf…ff58
7 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0x744138db…a855
0x34b655…2a6f
6 touches
3 conflicts
0x36e357c3…d325
0x34b655…2a6f
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
15 conflicts on slot 0x310afe2cd5…d683e1
Audit this contract →
← previous block·next block →recent activity