← previous blocknext block →recent activity
Analyzing
Block #83,666,738
34 transactions · 31 stateful · 2026-06-25 19:51:30 UTC
Parallelism
56/100
Blocked
74%
Avg conflicts / tx
3.21
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,666,738 · 34 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w08w19w211w312w413w514w615w716w817w918w1019w1125w329w431w632w1233w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0xb6b7c45d…9d5a
0x34b655…2a6f
16 touches
28 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
14 touches
21 conflicts
0x5c3a40be…e25a
0x34b655…2a6f
12 touches
15 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
12 touches
15 conflicts
0xdf37a93d…879b
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x76477ddf…b8f8
0xc8689a…ee79
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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity