← previous blocknext block →recent activity
Analyzing
Block #84,574,444
18 transactions · 15 stateful · 2026-06-30 00:42:38 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,574,444 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w09w111w012w113w114w215w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec85756f…0ba2
0x34b655…2a6f
6 touches
3 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
0x34b655…2a6f
6 touches
3 conflicts
0x4bdcc5ee…7e90
0x34b655…2a6f
6 touches
3 conflicts
0x9edc0a7d…2724
0x34b655…2a6f
6 touches
3 conflicts
0x6a53b1c0…c3f2
0x34b655…2a6f
6 touches
3 conflicts
0xb44d5376…33cc
0x34b655…2a6f
5 touches
3 conflicts
0xbc9aaf19…8cfd
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
3 conflicts on slot 0xec85756fe1…f40ba2
Audit this contract →
← previous block·next block →recent activity