← previous blocknext block →recent activity
Analyzing
Block #83,653,157
27 transactions · 20 stateful · 2026-06-25 18:21:01 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,653,157 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w09w113w014w118w220w121w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x785889c9…0603
0x34b655…2a6f
8 touches
6 conflicts
0x18904470…0ef9
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xc8fec9ca…2d60
0x34b655…2a6f
6 touches
3 conflicts
0x5501f715…c3a6
0xd32edf…ff58
5 touches
3 conflicts
0x7527802e…2ba9
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
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
6 conflicts on slot 0x785889c9fb…160603
Audit this contract →
← previous block·next block →recent activity