← previous blocknext block →recent activity
Analyzing
Block #84,292,161
13 transactions · 13 stateful · 2026-06-28 17:20:13 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,292,161 · 13 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
6w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
6 touches
3 conflicts
0x7d722ca2…ab3c
0x34b655…2a6f
6 touches
3 conflicts
0xd2cdfa3f…f071
0x34b655…2a6f
6 touches
3 conflicts
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0x97d5efed…1aa4
0x34b655…2a6f
4 touches
1 conflict
0xa49c9d72…616f
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity