← previous blocknext block →recent activity
Analyzing
Block #82,269,006
10 transactions · 10 stateful · 2026-06-19 08:14:05 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,269,006 · 10 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x4a4ad8c0…fcd8
0x065c9d…c394
4 touches
1 conflict
0x97074a11…3764
0x065c9d…c394
3 touches
1 conflict
0x291685cb…c84d
0x065c9d…c394
3 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x3f86f9c3…14f7
0x34b655…2a6f
2 touches
0 conflicts
0x60d07066…695c
0x34b655…2a6f
2 touches
0 conflicts
0x6da7e49a…4bc5
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