← previous blocknext block →recent activity
Analyzing
Block #82,273,429
26 transactions · 20 stateful · 2026-06-19 08:43:30 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,273,429 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w114w015w117w119w221w224w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06ab8d8…3589
0x34b655…2a6f
8 touches
6 conflicts
0xf7c4b697…912f
0x34b655…2a6f
6 touches
3 conflicts
0x9cc13b7b…c0ac
0xa6afd3…d132
6 touches
3 conflicts
0x3d34f2bd…5d63
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc3eedc44…373f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0xf06ab8d81b…9b3589
Audit this contract →
← previous block·next block →recent activity