← previous blocknext block →recent activity
Analyzing
Block #83,580,129
15 transactions · 14 stateful · 2026-06-25 10:13:14 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,580,129 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w412w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24d68cf2…09b7
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0xe64e6363…e676
0x34b655…2a6f
6 touches
3 conflicts
0x4e1ce17e…98a7
0x34b655…2a6f
4 touches
1 conflict
0x1586f0ea…6b96
0x34b655…2a6f
4 touches
1 conflict
0x65bb8d8c…8bb0
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
10 conflicts on slot 0x24d68cf28e…9209b7
Audit this contract →
← previous block·next block →recent activity