← previous blocknext block →recent activity
Analyzing
Block #94,468,172
15 transactions · 15 stateful · 2026-08-09 10:42:28 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,468,172 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w110w011w112w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0x0cc9b2…7777
6 touches
3 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
6 touches
3 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
6 touches
3 conflicts
0x00000000…0008
0x0ea966…0742
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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: MONI (MONI)
3 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity