← previous blocknext block →recent activity
Analyzing
Block #91,412,038
17 transactions · 16 stateful · 2026-07-29 18:12:12 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,412,038 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w28w39w410w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0x0cc9b2…7777
8 touches
6 conflicts
0x00000000…0008
0x0ea966…0742
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
8 touches
6 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x41f1e2e5…2edf
0x34b655…2a6f
6 touches
3 conflicts
0x4fa2386a…7e33
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)
6 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity