← previous blocknext block →recent activity
Analyzing
Block #82,019,384
17 transactions · 13 stateful · 2026-06-18 04:29:15 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,019,384 · 17 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
1w04w05w18w09w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0x7d179925…2f45
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x4ad1ccee…bcd0
0x065c9d…c394
4 touches
1 conflict
0x7240b70b…0e2d
0x34b655…2a6f
2 touches
0 conflicts
0x76e85a07…5ff1
0x34b655…2a6f
2 touches
0 conflicts
0xa47bd963…32db
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 0x557cd4fad5…e4228c
Audit this contract →
← previous block·next block →recent activity