← previous blocknext block →recent activity
Analyzing
Block #106,283,326
18 transactions · 15 stateful · 2026-09-19 21:23:02 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,283,326 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w19w010w112w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a6ee6c4…7c39
0xa6afd3…d132
4 touches
1 conflict
0x33387c27…44cc
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1ba56ec2…25e4
0xa6afd3…d132
4 touches
1 conflict
0xb05cd4f5…73d0
0x34ae4d…3fc5
2 touches
0 conflicts
0xdb067026…9eb8
0x34ae4d…3fc5
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-WETH/USDC
1 conflict on slot 0x5a6ee6c4d7…157c39
Audit this contract →
← previous block·next block →recent activity