← previous blocknext block →recent activity
Analyzing
Block #82,267,844
12 transactions · 11 stateful · 2026-06-19 08:06:20 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,267,844 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x63eec40e…b8f7
0x065c9d…c394
4 touches
1 conflict
0x6f4c97c7…f4c0
0x065c9d…c394
3 touches
1 conflict
0xa34dc0c7…224e
0x065c9d…c394
3 touches
1 conflict
0x00000000…009a
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…9e49
0x16f70c…c3dd
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0xac2a0273…7212
0x34b655…2a6f
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 0xd8dd03ce37…9cdc8d
Audit this contract →
← previous block·next block →recent activity