← previous blocknext block →recent activity
Analyzing
Block #83,615,500
37 transactions · 34 stateful · 2026-06-25 14:09:25 UTC
Parallelism
68/100
Blocked
65%
Avg conflicts / tx
2.43
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #83,615,500 · 37 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w08w39w410w511w613w014w115w216w317w418w519w620w721w822w923w1024w1125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0x94e7f277…471b
0x34b655…2a6f
10 touches
10 conflicts
0x98d3fc79…df78
0x34b655…2a6f
10 touches
10 conflicts
0xf8fd1cbd…d093
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdf37a93d…879b
0x34b655…2a6f
8 touches
6 conflicts
0x03fb27fd…0c06
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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity