← previous blocknext block →recent activity
Analyzing
Block #83,626,318
58 transactions · 42 stateful · 2026-06-25 15:21:44 UTC
Parallelism
71/100
Blocked
67%
Avg conflicts / tx
2.47
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,626,318 · 58 txs across 17 waves · depth 17
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
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w16w09w112w213w314w425w028w131w437w1038w1139w1240w1345w546w647w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0xe02484a6…c32e
0xc8689a…ee79
12 touches
15 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
12 touches
15 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
12 touches
15 conflicts
0x5fad6fee…7714
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
10 touches
10 conflicts
0xdb19247d…233c
0x34b655…2a6f
10 touches
10 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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity