← previous blocknext block →recent activity
Analyzing
Block #82,667,093
19 transactions · 17 stateful · 2026-06-21 04:33:11 UTC
Parallelism
68/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #82,667,093 · 19 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
3w04w06w17w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb43dc900…22f2
0xa6afd3…d132
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x76d1e78d…7877
0x40c49f…2af0
4 touches
1 conflict
0xcbe9b09a…4988
0x080ec9…fe74
2 touches
0 conflicts
0xe8adf936…34b0
0x188d58…ea8e
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity