← previous blocknext block →recent activity
Analyzing
Block #106,388,207
16 transactions · 16 stateful · 2026-09-20 06:10:50 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,388,207 · 16 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
1w06w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7b95944e…03c5
0x065c9d…c394
3 touches
1 conflict
0x1884cf6d…4bbe
0x065c9d…c394
2 touches
0 conflicts
0x41a22749…c23f
0x065c9d…c394
2 touches
0 conflicts
0x4f586ee8…47c1
0x065c9d…c394
2 touches
0 conflicts
0xcfa1d70e…173a
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity