← previous blocknext block →recent activity
Analyzing
Block #106,464,156
16 transactions · 16 stateful · 2026-09-20 12:33:07 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,464,156 · 16 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
2w09w010w112w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x206a4507…e6c3
0x34b655…2a6f
4 touches
1 conflict
0x01442500…23e3
0x065c9d…c394
4 touches
1 conflict
0x1f396cee…862f
0x34b655…2a6f
4 touches
1 conflict
0x2c0fb06b…d0bc
0x065c9d…c394
3 touches
1 conflict
0xe3c4c02e…bc49
0x065c9d…c394
3 touches
1 conflict
0x876fa6c4…7795
0x34b655…2a6f
2 touches
0 conflicts
0xca841faa…486a
0x34b655…2a6f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity