← previous blocknext block →recent activity
Analyzing
Block #94,978,692
14 transactions · 14 stateful · 2026-08-11 05:31:48 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,978,692 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x705ab4ae…0162
0x34b655…2a6f
6 touches
3 conflicts
0x5a884e80…ed8a
0x34b655…2a6f
6 touches
3 conflicts
0x800ff80d…df9e
0x34b655…2a6f
5 touches
3 conflicts
0xdcc6663d…abd1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
2 touches
0 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
10 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity