← previous blocknext block →recent activity
Analyzing
Block #84,334,302
27 transactions · 22 stateful · 2026-06-28 22:00:56 UTC
Parallelism
81/100
Blocked
59%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,334,302 · 27 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
1w02w13w24w05w16w29w210w311w414w015w116w217w318w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x7c6984da…21e5
0x34b655…2a6f
8 touches
6 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
6 touches
3 conflicts
0xe75ce681…ba60
0x188d58…ea8e
6 touches
3 conflicts
0x75194ada…a1c5
0x34b655…2a6f
6 touches
3 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xda7f9bd2…e332
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity