← previous blocknext block →recent activity
Analyzing
Block #106,018,334
16 transactions · 13 stateful · 2026-09-18 23:09:20 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,018,334 · 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
1w04w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xb9eb76d3…f80c
0x065c9d…c394
3 touches
1 conflict
0x1f552b2b…2506
0x065c9d…c394
3 touches
1 conflict
0x23f2f337…4cb6
0x065c9d…c394
3 touches
1 conflict
0xa605468c…1bfc
0x34ae4d…3fc5
2 touches
0 conflicts
0x00c1b478…b9e6
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