← previous blocknext block →recent activity
Analyzing
Block #102,492,062
26 transactions · 17 stateful · 2026-09-06 14:25:31 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,492,062 · 26 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
2w06w07w18w09w010w112w013w114w220w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xe23824ec…66c2
0x5df178…7777
2 touches
1 conflict
0x00000000…0000
0x2c492d…444e
2 touches
0 conflicts
0x00000000…0002
0x2c492d…444e
2 touches
0 conflicts
0x00000000…0003
0x2c492d…444e
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