← previous blocknext block →recent activity
Analyzing
Block #105,930,979
32 transactions · 28 stateful · 2026-09-18 15:49:31 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,930,979 · 32 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
1w02w03w04w16w27w08w09w110w223w124w025w126w227w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdb11940a…519b
0x34b655…2a6f
6 touches
3 conflicts
0xefb236ca…f49b
0x34b655…2a6f
6 touches
3 conflicts
0x11a61991…ed74
0x34b655…2a6f
4 touches
1 conflict
0x2fba77e7…bea1
0x34b655…2a6f
4 touches
1 conflict
0xa5f71148…62ee
0x40c49f…2af0
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