← previous blocknext block →recent activity
Analyzing
Block #102,655,364
10 transactions · 10 stateful · 2026-09-07 04:12:14 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,655,364 · 10 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
1w02w03w17w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xacf0d67f…184d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x5718fb81…32c3
0x40c49f…2af0
4 touches
1 conflict
0x0a6db9cc…cd4b
0x34b655…2a6f
2 touches
0 conflicts
0x1513b999…b52e
0x34b655…2a6f
2 touches
0 conflicts
0x1e4cc7e7…b4d3
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