← previous blocknext block →recent activity
Analyzing
Block #104,192,923
16 transactions · 14 stateful · 2026-09-12 13:35:24 UTC
Parallelism
81/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,192,923 · 16 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
1w02w111w015w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9e4c62e…8580
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x07574c24…1dad
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3ba1851b…6c0c
0x065c9d…c394
3 touches
1 conflict
0x3ba1851b…6c0d
0x065c9d…c394
3 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 0xe9e4c62ef3…f58580
Audit this contract →
← previous block·next block →recent activity