← previous blocknext block →recent activity
Analyzing
Block #94,791,624
34 transactions · 31 stateful · 2026-08-10 13:50:51 UTC
Parallelism
50/100
Blocked
68%
Avg conflicts / tx
3.47
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #94,791,624 · 34 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w27w38w49w411w512w613w714w615w816w917w1023w1124w1229w1430w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
18 touches
36 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 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
36 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity