← previous blocknext block →recent activity
Analyzing
Block #82,656,821
10 transactions · 7 stateful · 2026-06-21 03:24:14 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,656,821 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0x7ba3d4ba…d55a
0xc8689a…ee79
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
2 touches
0 conflicts
0x0bf5b45b…7be3
0x34b655…2a6f
2 touches
0 conflicts
0x189e374d…c093
0x34b655…2a6f
2 touches
0 conflicts
0x1c9a5ef8…03fb
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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: Perpl
1 conflict on slot 0x0efc210ee8…0e70ab
Audit this contract →
← previous block·next block →recent activity