← previous blocknext block →recent activity
Analyzing
Block #106,100,876
18 transactions · 16 stateful · 2026-09-19 06:04:43 UTC
Parallelism
83/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,100,876 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w014w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x9057e0ca…fb47
0x34b655…2a6f
4 touches
1 conflict
0xfb310e2d…f9d3
0x34b655…2a6f
4 touches
1 conflict
0x6658fa82…4017
0x754704…b603
2 touches
0 conflicts
0xc7e70be2…b0c3
0x754704…b603
2 touches
0 conflicts
0xf371c34e…e4ac
0x754704…b603
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: MarginAccount
1 conflict on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity