← previous blocknext block →recent activity
Analyzing
Block #83,410,804
29 transactions · 27 stateful · 2026-06-24 15:23:30 UTC
Parallelism
66/100
Blocked
67%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,410,804 · 29 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
1w02w14w26w37w08w19w210w311w412w513w614w715w826w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x967b4a40…7a78
0x34b655…2a6f
12 touches
15 conflicts
0xa1571d54…ae41
0x34b655…2a6f
10 touches
10 conflicts
0x9c7571b3…9605
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xbb6488a9…7232
0x34b655…2a6f
8 touches
6 conflicts
0xef29696a…e7bd
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity