← previous blocknext block →recent activity
Analyzing
Block #91,408,973
16 transactions · 15 stateful · 2026-07-29 17:56:40 UTC
Parallelism
50/100
Blocked
60%
Avg conflicts / tx
1.94
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,408,973 · 16 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
3w04w15w27w08w19w210w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0xe4f6e7…9657
16 touches
28 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
16 touches
28 conflicts
0x00000000…0008
0x0ea966…0742
16 touches
28 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc550cc48…815e
0x34b655…2a6f
4 touches
1 conflict
0x70a7b5d6…fe0e
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: 0xe4f6e757…919657
28 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity