← previous blocknext block →recent activity
Analyzing
Block #84,522,288
7 transactions · 6 stateful · 2026-06-29 18:54:22 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,522,288 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfff39462…a61b
0x34b655…2a6f
4 touches
1 conflict
0x3149127f…19a9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb9f5f3bf…5f6c
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0x67fc285e…2584
0x34b655…2a6f
2 touches
0 conflicts
0xd5cb84c6…abb3
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 0xfff3946255…51a61b
Audit this contract →
← previous block·next block →recent activity