← previous blocknext block →recent activity
Analyzing
Block #94,913,633
23 transactions · 23 stateful · 2026-08-11 00:04:35 UTC
Parallelism
61/100
Blocked
57%
Avg conflicts / tx
1.96
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #94,913,633 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd66696e0…0842
0x34b655…2a6f
16 touches
28 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
12 touches
15 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
12 touches
15 conflicts
0xff3d91c4…1a37
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity