← previous blocknext block →recent activity
Analyzing
Block #91,404,776
11 transactions · 9 stateful · 2026-07-29 17:35:24 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,404,776 · 11 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
2w03w15w06w17w28w3
- 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
0x44ad89ba…cf83
0xe4f6e7…9657
8 touches
6 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x21280422…0930
0x34b655…2a6f
2 touches
0 conflicts
0x3e033d91…5255
0x34b655…2a6f
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)
6 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity