← previous blocknext block →recent activity
Analyzing
Block #104,165,789
20 transactions · 13 stateful · 2026-09-12 11:17:52 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,165,789 · 20 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
5w06w014w115w017w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e2812f6…3518
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0002
0x47bae1…7568
4 touches
1 conflict
0x00000000…0004
0x47bae1…7568
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x56a919c4…ab49
0xe7cd86…c82d
4 touches
1 conflict
0x66312019…f62e
0xe7cd86…c82d
4 touches
1 conflict
0x6237f1a7…2f59
0x3bd359…433a
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x5e2812f63b…a23518
Audit this contract →
← previous block·next block →recent activity