← previous blocknext block →recent activity
Analyzing
Block #106,155,424
12 transactions · 11 stateful · 2026-09-19 10:39:15 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,155,424 · 12 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
1w02w03w16w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xa2f97eb1…f8ec
0x34b655…2a6f
4 touches
1 conflict
0xe33b6fa2…e16b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x2aa7be4c…0f84
0x34b655…2a6f
2 touches
0 conflicts
0x39910194…6b11
0x34b655…2a6f
2 touches
0 conflicts
0x4955ca17…cbb8
0x34b655…2a6f
2 touches
0 conflicts
0x4b589704…e771
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: MarginAccount
1 conflict on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity