← previous blocknext block →recent activity
Analyzing
Block #83,398,542
25 transactions · 20 stateful · 2026-06-24 14:01:30 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,398,542 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w08w19w210w311w412w513w615w724w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x9c7571b3…9605
0x34b655…2a6f
8 touches
6 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 conflicts
0xb6632320…a3ce
0x34b655…2a6f
8 touches
6 conflicts
0xc696771b…b53d
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xba7cfb09…e5d3
0x34b655…2a6f
6 touches
3 conflicts
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