← previous blocknext block →recent activity
Analyzing
Block #83,889,624
25 transactions · 23 stateful · 2026-06-26 20:38:39 UTC
Parallelism
76/100
Blocked
61%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,889,624 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w38w010w013w114w215w316w417w118w219w220w122w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32229dd3…4dbb
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7682e08a…2de9
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xd996735f…872e
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
6 conflicts on slot 0x32229dd3a6…874dbb
Audit this contract →
← previous block·next block →recent activity