← previous blocknext block →recent activity
Analyzing
Block #82,729,411
16 transactions · 13 stateful · 2026-06-21 11:29:21 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,729,411 · 16 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
1w02w13w210w011w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x2fd12b6c…02cc
0x34b655…2a6f
6 touches
3 conflicts
0x50a88d10…679c
0x34b655…2a6f
6 touches
3 conflicts
0x38d1779d…0fbc
0xd32edf…ff58
5 touches
3 conflicts
0xd89f212d…2bbf
0x34b655…2a6f
4 touches
1 conflict
0x32409e80…a396
0x34b655…2a6f
4 touches
1 conflict
0xe6e45a35…0627
0x34b655…2a6f
4 touches
1 conflict
0xfecb18c0…01ed
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity