← previous blocknext block →recent activity
Analyzing
Block #83,652,474
16 transactions · 16 stateful · 2026-06-25 18:16:28 UTC
Parallelism
44/100
Blocked
50%
Avg conflicts / tx
2.31
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,652,474 · 16 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w612w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46d5a052…ff2e
0x34b655…2a6f
18 touches
36 conflicts
0x77fc7d81…0a40
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xc34f7ec0…59cd
0x34b655…2a6f
10 touches
10 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
10 touches
10 conflicts
0x00076632…7bf7
0x34b655…2a6f
8 touches
6 conflicts
0x74fd0a9b…3aaa
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
36 conflicts on slot 0x46d5a0529d…adff2e
Audit this contract →
← previous block·next block →recent activity