← previous blocknext block →recent activity
Analyzing
Block #102,855,284
20 transactions · 18 stateful · 2026-09-07 21:01:19 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,855,284 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w28w39w410w511w116w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5b09bf44…5907
0xa6afd3…d132
4 touches
1 conflict
0x6d8ad688…4bf5
0xa6afd3…d132
4 touches
1 conflict
0x40970e69…da50
0x34ae4d…3fc5
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
10 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity