← previous blocknext block →recent activity
Analyzing
Block #94,759,360
17 transactions · 14 stateful · 2026-08-10 11:08:34 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,759,360 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w08w19w211w312w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0x4cb81411…37f6
0x34b655…2a6f
6 touches
3 conflicts
0xf3383813…4a0c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x5e71af98…bfd6
0x34b655…2a6f
4 touches
1 conflict
0xb0608dfe…083d
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity