← previous blocknext block →recent activity
Analyzing
Block #82,020,777
12 transactions · 9 stateful · 2026-06-18 04:38:32 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,020,777 · 12 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
10w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38d0f220…01f4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5c40bbe4…5180
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
2 touches
0 conflicts
0xa9988419…9f45
0x34b655…2a6f
2 touches
0 conflicts
0xfe39a1f7…8eb0
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 0x38d0f220b3…5301f4
Audit this contract →
← previous block·next block →recent activity