← previous blocknext block →recent activity
Analyzing
Block #82,642,273
18 transactions · 10 stateful · 2026-06-21 01:46:42 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,642,273 · 18 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
2w03w19w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3eedc44…373f
0x34b655…2a6f
4 touches
1 conflict
0xf2038797…088c
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x3d158563…8713
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xf87dc17c…8b99
0x34b655…2a6f
3 touches
1 conflict
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: Perpl
1 conflict on slot 0xc3eedc448d…c6373f
Audit this contract →
← previous block·next block →recent activity