← previous blocknext block →recent activity
Analyzing
Block #102,741,476
24 transactions · 20 stateful · 2026-09-07 11:25:29 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,741,476 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w29w014w217w318w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
4 touches
1 conflict
0x3643741b…109c
0x34b655…2a6f
4 touches
1 conflict
0x5f251b96…6054
0x34b655…2a6f
4 touches
1 conflict
0x5f46663c…b4c2
0x34b655…2a6f
4 touches
1 conflict
0x742ce0ab…3c47
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: Kuru Exchange: Market-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity