← previous blocknext block →recent activity
Analyzing
Block #83,844,913
31 transactions · 26 stateful · 2026-06-26 15:40:25 UTC
Parallelism
77/100
Blocked
54%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,844,913 · 31 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
1w02w13w25w06w39w010w112w113w014w115w216w317w418w519w627w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe560375e…4626
0x34b655…2a6f
8 touches
6 conflicts
0x8726ff39…3be8
0x34b655…2a6f
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x5c591136…d322
0x34b655…2a6f
8 touches
6 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
8 touches
6 conflicts
0x470c91cd…ffe8
0xd32edf…ff58
7 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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity