← previous blocknext block →recent activity
Analyzing
Block #104,916,239
24 transactions · 20 stateful · 2026-09-15 02:39:57 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,916,239 · 24 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
2w03w16w07w010w113w114w222w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97426111…a4c2
0x065c9d…c394
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0000
0x33a247…6221
4 touches
1 conflict
0x5b198300…5e8a
0x33a247…6221
4 touches
1 conflict
0x6b838aa1…d902
0x33a247…6221
4 touches
1 conflict
0x7e936ae9…f41f
0x33a247…6221
4 touches
1 conflict
0xc3d42934…1d81
0x33a247…6221
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
1 conflict on slot 0x9742611173…4da4c2
Audit this contract →
← previous block·next block →recent activity