← previous blocknext block →recent activity
Analyzing
Block #95,721,652
14 transactions · 13 stateful · 2026-08-13 20:04:15 UTC
Parallelism
43/100
Blocked
62%
Avg conflicts / tx
2.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,721,652 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0x0cc9b2…7777
16 touches
28 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
16 touches
28 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
16 touches
28 conflicts
0x00000000…0008
0x0ea966…0742
16 touches
28 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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: MONI (MONI)
28 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity