← previous blocknext block →recent activity
Analyzing
Block #106,223,802
10 transactions · 9 stateful · 2026-09-19 16:23:25 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,223,802 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xd9b1cc08…0c1f
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x20433cf7…4727
0x40c49f…2af0
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
2 touches
0 conflicts
0xa931dc5e…5170
0x065c9d…c394
2 touches
0 conflicts
0xd3f7d372…8dcc
0x065c9d…c394
2 touches
0 conflicts
0xdf13f259…c909
0x065c9d…c394
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
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity