← previous blocknext block →recent activity
Analyzing
Block #83,633,482
35 transactions · 29 stateful · 2026-06-25 16:09:37 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,633,482 · 35 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
1w02w04w17w08w19w210w311w012w113w014w115w216w318w419w524w128w229w330w433w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xaa7ee7…f0e4
8 touches
6 conflicts
0xf4b4898d…f948
0x34b655…2a6f
8 touches
6 conflicts
0xb3975d93…b4a2
0x34b655…2a6f
6 touches
3 conflicts
0x23bcb6e8…566e
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xba582b89…9f62
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity