← previous blocknext block →recent activity
Analyzing
Block #105,643,051
61 transactions · 28 stateful · 2026-09-17 15:38:04 UTC
Parallelism
93/100
Blocked
32%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,643,051 · 61 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
1w02w13w24w39w010w112w213w323w025w026w128w254w1
- 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
0xb686e6f5…f6d1
0xc8689a…ee79
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0x06e40499…165e
0x34ae4d…3fc5
8 touches
6 conflicts
0xd35bb5ac…3586
0x065c9d…c394
8 touches
6 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
8 touches
6 conflicts
0x95be7768…e3af
0xd32edf…ff58
7 touches
6 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