← previous blocknext block →recent activity
Analyzing
Block #83,638,514
14 transactions · 13 stateful · 2026-06-25 16:43:16 UTC
Parallelism
57/100
Blocked
62%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,638,514 · 14 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
2w03w15w26w37w48w59w010w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7468e81…86e5
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0xe64e6363…e676
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
4 touches
1 conflict
0xa1763ef4…5892
0x34b655…2a6f
4 touches
1 conflict
0xb453da85…e48f
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 0xf7468e81f0…5b86e5
Audit this contract →
← previous block·next block →recent activity