← previous blocknext block →recent activity
Analyzing
Block #82,640,390
16 transactions · 11 stateful · 2026-06-21 01:34:07 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,640,390 · 16 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
1w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x0b1cd73b…cc68
0x065c9d…c394
4 touches
1 conflict
0x4b174202…df5e
0x065c9d…c394
2 touches
0 conflicts
0x60b24061…7c23
0x188d58…ea8e
2 touches
0 conflicts
0x60b24061…7c25
0x188d58…ea8e
2 touches
0 conflicts
0x9413ddeb…70dd
0x188d58…ea8e
2 touches
0 conflicts
0x557cd4fa…228c
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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 0x7d42dc8b22…fefdb6
Audit this contract →
← previous block·next block →recent activity