← previous blocknext block →recent activity
Analyzing
Block #84,185,726
40 transactions · 33 stateful · 2026-06-28 05:30:59 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
1.9
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #84,185,726 · 40 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w29w311w012w115w016w117w218w319w420w521w622w123w724w432w833w934w1035w1136w1237w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75cdffd8…c217
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 touches
6 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
8 touches
6 conflicts
0xab86573c…682e
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 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
21 conflicts on slot 0x75cdffd8c9…dec217
Audit this contract →
← previous block·next block →recent activity