← previous blocknext block →recent activity
Analyzing
Block #94,668,523
18 transactions · 18 stateful · 2026-08-10 03:30:12 UTC
Parallelism
61/100
Blocked
44%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,668,523 · 18 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
1w02w13w25w36w49w412w514w616w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e52e46…0894
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xf18575c0…880c
0x34b655…2a6f
4 touches
1 conflict
0xfb31d278…9107
0x34b655…2a6f
4 touches
1 conflict
0x15c22181…1354
0x34b655…2a6f
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0xbfc5d23d…6ad7
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 0xe2e52e4663…6f0894
Audit this contract →
← previous block·next block →recent activity