← previous blocknext block →recent activity
Analyzing
Block #82,563,319
23 transactions · 18 stateful · 2026-06-20 16:57:45 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,563,319 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w210w312w413w515w619w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b305a3b…1c35
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x8b305a3b…1c34
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd3a433e6…2fad
0x34b655…2a6f
10 touches
10 conflicts
0xfbabb02d…af07
0x34b655…2a6f
6 touches
3 conflicts
0x468992af…e03e
0x34b655…2a6f
6 touches
3 conflicts
0x6713b018…05f3
0x34b655…2a6f
4 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
21 conflicts on slot 0x8b305a3b6b…0c1c35
Audit this contract →
← previous block·next block →recent activity