← previous blocknext block →recent activity
Analyzing
Block #84,289,169
25 transactions · 24 stateful · 2026-06-28 17:00:15 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,289,169 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w29w210w111w013w114w015w116w217w318w420w321w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
10 touches
10 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
10 touches
10 conflicts
0x00000000…0003
0x019883…2a9a
10 touches
10 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa10c86f8…4b74
0x3bd359…433a
10 touches
10 conflicts
0xa472d565…9fe4
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0000
0x019883…2a9a
10 touches
10 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 0xab86573c9c…f3682e
Audit this contract →
← previous block·next block →recent activity