← previous blocknext block →recent activity
Analyzing
Block #84,461,432
20 transactions · 18 stateful · 2026-06-29 12:08:20 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,461,432 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w19w010w112w213w314w415w516w617w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0xfebf4166…9bf2
0x34b655…2a6f
6 touches
3 conflicts
0xf3e2e78c…c2e3
0x34b655…2a6f
6 touches
3 conflicts
0xe560375e…4626
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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