← previous blocknext block →recent activity
Analyzing
Block #83,493,966
18 transactions · 16 stateful · 2026-06-25 00:38:42 UTC
Parallelism
61/100
Blocked
56%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,493,966 · 18 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
1w02w03w15w17w08w19w210w311w412w513w617w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x76477ddf…b8f8
0xc8689a…ee79
6 touches
3 conflicts
0x226b141d…1864
0x34b655…2a6f
6 touches
3 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
6 touches
3 conflicts
0x7527802e…2ba9
0x34b655…2a6f
6 touches
3 conflicts
0xa02e5cdd…76b8
0x34b655…2a6f
6 touches
3 conflicts
0xa432d0a7…ec31
0x34b655…2a6f
6 touches
3 conflicts
0x06af4e2a…9e9a
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity