← previous blocknext block →recent activity
Analyzing
Block #102,105,486
23 transactions · 23 stateful · 2026-09-05 05:46:39 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,105,486 · 23 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
1w02w03w15w26w38w110w013w014w116w117w218w219w320w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xf5a19743…decb
0x34b655…2a6f
6 touches
3 conflicts
0xeb12640d…f4f6
0x065c9d…c394
5 touches
3 conflicts
0x88cc3fb2…7cce
0x065c9d…c394
5 touches
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity