← previous blocknext block →recent activity
Analyzing
Block #83,617,703
42 transactions · 37 stateful · 2026-06-25 14:24:09 UTC
Parallelism
64/100
Blocked
62%
Avg conflicts / tx
2.71
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,617,703 · 42 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w08w39w410w014w015w116w217w318w419w520w621w722w823w924w1025w139w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xd06d821c…e5d0
0x34b655…2a6f
14 touches
21 conflicts
0x5a5dd7b4…fba4
0x34b655…2a6f
10 touches
10 conflicts
0xd7add284…8d28
0x34b655…2a6f
10 touches
10 conflicts
0x485d2778…aa5d
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x6cf2a1e7…e1e1
0x34b655…2a6f
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
55 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity