← previous blocknext block →recent activity
Analyzing
Block #94,852,673
20 transactions · 20 stateful · 2026-08-10 18:58:00 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,852,673 · 20 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
1w02w13w04w25w36w07w18w39w410w515w616w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51611059…097e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x1ea2b1f6…1d57
0x34b655…2a6f
4 touches
1 conflict
0x1ea2b1f6…1d58
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0x516110595e…7a097e
Audit this contract →
← previous block·next block →recent activity