← previous blocknext block →recent activity
Analyzing
Block #102,477,618
11 transactions · 10 stateful · 2026-09-06 13:12:10 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,477,618 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x958b5aee…b0b3
0x065c9d…c394
4 touches
1 conflict
0x70d81211…f49f
0x34b655…2a6f
4 touches
1 conflict
0x782b660c…b99b
0x34b655…2a6f
4 touches
1 conflict
0xf62a6491…72fd
0x065c9d…c394
3 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0x9dd365a3…8743
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
0x34ae4d…3fc5
2 touches
0 conflicts
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 0x958b5aee77…84b0b3
Audit this contract →
← previous block·next block →recent activity