← previous blocknext block →recent activity
Analyzing
Block #82,265,396
19 transactions · 13 stateful · 2026-06-19 07:50:01 UTC
Parallelism
84/100
Blocked
23%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,265,396 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0a2c05f7…8716
0x065c9d…c394
3 touches
1 conflict
0x729d856f…b960
0xd32edf…ff58
3 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x09ef45e2…5677
0x5afd3e…7620
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
1 conflict on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity