← previous blocknext block →recent activity
Analyzing
Block #94,686,875
18 transactions · 13 stateful · 2026-08-10 05:02:31 UTC
Parallelism
61/100
Blocked
62%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,686,875 · 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
1w02w13w04w15w28w310w411w512w615w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4eb691ce…350c
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xe2e52e46…0894
0x34b655…2a6f
6 touches
3 conflicts
0x57bff3a8…86f3
0x34b655…2a6f
6 touches
3 conflicts
0x72c8aeb2…9921
0x34b655…2a6f
4 touches
1 conflict
0x8e521e54…a2ff
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 0x4eb691cec6…a4350c
Audit this contract →
← previous block·next block →recent activity