← previous blocknext block →recent activity
Analyzing
Block #82,793,428
26 transactions · 22 stateful · 2026-06-21 18:36:36 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,793,428 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w17w08w29w310w314w116w217w421w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x2df5bd93…9e2d
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
6 touches
3 conflicts
0x9fb55ee7…8ecc
0xa6afd3…d132
6 touches
3 conflicts
0xfac61869…a55d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity