← previous blocknext block →recent activity
Analyzing
Block #106,810,402
24 transactions · 22 stateful · 2026-09-21 17:36:45 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,810,402 · 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
2w03w14w26w07w110w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
4 touches
1 conflict
0xa93fef74…94b3
0x37db7f…ec7b
4 touches
1 conflict
0xdbcc4ab8…2aba
0x37db7f…ec7b
4 touches
1 conflict
0xe3e67fe3…e754
0x37db7f…ec7b
4 touches
1 conflict
0x2877f440…c2c8
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity