← previous blocknext block →recent activity
Analyzing
Block #81,878,911
18 transactions · 16 stateful · 2026-06-17 12:50:49 UTC
Parallelism
61/100
Blocked
38%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #81,878,911 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w48w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x3181bd2d…cf15
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x79b6c431…96ad
0x065c9d…c394
4 touches
1 conflict
0x6cd9f618…bdb2
0x1111b3…4111
2 touches
0 conflicts
0xad436b12…f632
0x1111b3…4111
2 touches
0 conflicts
0xf8ff11a5…a206
0x1111b3…4111
2 touches
0 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
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
15 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity