← previous blocknext block →recent activity
Analyzing
Block #83,636,462
19 transactions · 16 stateful · 2026-06-25 16:29:32 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,636,462 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w17w28w39w410w514w216w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3405238a…68b6
0x34b655…2a6f
12 touches
15 conflicts
0x0f653641…3956
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x1bcbf4c9…d744
0x34b655…2a6f
8 touches
6 conflicts
0x549502e8…9b94
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
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
15 conflicts on slot 0x3405238a6d…6268b6
Audit this contract →
← previous block·next block →recent activity