← previous blocknext block →recent activity
Analyzing
Block #82,643,890
13 transactions · 11 stateful · 2026-06-21 01:57:31 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,643,890 · 13 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
1w05w16w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x541021b0…93b9
0x065c9d…c394
2 touches
0 conflicts
0x7dffdb47…6cc6
0x065c9d…c394
2 touches
0 conflicts
0x8d8d6c6d…9f57
0x065c9d…c394
2 touches
0 conflicts
0xa22d4b58…26a0
0x065c9d…c394
2 touches
0 conflicts
0xb9fc22aa…118d
0x065c9d…c394
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity