← previous blocknext block →recent activity
Analyzing
Block #94,969,025
18 transactions · 17 stateful · 2026-08-11 04:43:11 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,969,025 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w211w012w114w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x588380ee…0a5c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xdf5075b5…e536
0x851145…3f07
4 touches
1 conflict
0x0edf889a…ce9d
0x01bff4…1071
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
3 conflicts on slot 0x588380ee30…d00a5c
Audit this contract →
← previous block·next block →recent activity