← previous blocknext block →recent activity
Analyzing
Block #84,488,328
24 transactions · 19 stateful · 2026-06-29 15:07:48 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,488,328 · 24 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
1w09w110w011w112w213w314w417w018w119w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
8 touches
6 conflicts
0x44966858…1d1a
0x34b655…2a6f
8 touches
6 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xee757899…302b
0x34b655…2a6f
6 touches
3 conflicts
0x44931115…3703
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity