← previous blocknext block →recent activity
Analyzing
Block #83,661,412
21 transactions · 19 stateful · 2026-06-25 19:15:59 UTC
Parallelism
52/100
Blocked
58%
Avg conflicts / tx
1.05
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,661,412 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w19w210w311w412w513w614w717w018w819w920w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16dce2e7…6f05
0x34b655…2a6f
10 touches
10 conflicts
0xc699b573…1f82
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0xf86f15cd…38af
0x34b655…2a6f
6 touches
3 conflicts
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x478e6e08…83bf
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 0x16dce2e7df…1b6f05
Audit this contract →
← previous block·next block →recent activity