← previous blocknext block →recent activity
Analyzing
Block #84,488,817
19 transactions · 15 stateful · 2026-06-29 15:11:04 UTC
Parallelism
74/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,488,817 · 19 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
1w02w17w08w19w210w311w216w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75cdffd8…c217
0x34b655…2a6f
8 touches
6 conflicts
0x975680c7…0e39
0xa6afd3…d132
6 touches
3 conflicts
0xee757899…302b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x44931115…3703
0x34b655…2a6f
4 touches
1 conflict
0x44966858…1d1a
0x34b655…2a6f
4 touches
1 conflict
0x636b2053…9114
0x34b655…2a6f
4 touches
1 conflict
0xdd20603d…518c
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
6 conflicts on slot 0x75cdffd8c9…dec217
Audit this contract →
← previous block·next block →recent activity