← previous blocknext block →recent activity
Analyzing
Block #102,867,372
30 transactions · 27 stateful · 2026-09-07 22:02:08 UTC
Parallelism
87/100
Blocked
41%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,867,372 · 30 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
3w04w15w26w37w08w110w011w113w215w016w119w223w124w025w229w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xc21def1b…c24d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb31eb7d3…64eb
0xa6afd3…d132
6 touches
3 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x91508d45…318b
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity