← previous blocknext block →recent activity
Analyzing
Block #84,495,308
18 transactions · 16 stateful · 2026-06-29 15:54:23 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,495,308 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w412w313w514w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2ca023f0…2eb8
0x34b655…2a6f
4 touches
1 conflict
0x344dbdb0…0cc0
0x34b655…2a6f
4 touches
1 conflict
0x393dfd73…ff57
0x34b655…2a6f
4 touches
1 conflict
0x742436a7…c4d4
0x34b655…2a6f
4 touches
1 conflict
0x90a9e3f8…17ab
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity