← previous blocknext block →recent activity
Analyzing
Block #83,759,508
26 transactions · 21 stateful · 2026-06-26 06:10:25 UTC
Parallelism
58/100
Blocked
62%
Avg conflicts / tx
2.27
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #83,759,508 · 26 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w09w110w211w312w413w514w615w716w817w918w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
22 touches
55 conflicts
0x4bdcc5ee…7e90
0x34b655…2a6f
10 touches
10 conflicts
0x58c659ec…3c6c
0x34b655…2a6f
10 touches
10 conflicts
0xcef70a96…db44
0x34b655…2a6f
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x4bcb740a…b738
0x40c49f…2af0
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
55 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity