← previous blocknext block →recent activity
Analyzing
Block #82,293,537
16 transactions · 14 stateful · 2026-06-19 10:57:39 UTC
Parallelism
69/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,293,537 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x3e1c3586…83d7
0xa6afd3…d132
4 touches
1 conflict
0xefdbc121…4869
0x40c49f…2af0
3 touches
1 conflict
0x6fffa762…dab7
0x40c49f…2af0
3 touches
1 conflict
0x75240e59…efa7
0x40c49f…2af0
2 touches
0 conflicts
0xd692f65b…ba86
0x40c49f…2af0
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity