← previous blocknext block →recent activity
Analyzing
Block #83,617,434
32 transactions · 21 stateful · 2026-06-25 14:22:21 UTC
Parallelism
84/100
Blocked
52%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,617,434 · 32 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
4w05w06w17w09w010w111w212w116w217w218w319w420w329w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f7ad3a0…de3b
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xff96dc9b…93d7
0x065c9d…c394
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x26c92234…e9bc
0x34b655…2a6f
4 touches
1 conflict
0x4efb974a…6126
0x34b655…2a6f
4 touches
1 conflict
0x58b9951c…1885
0x34b655…2a6f
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 0x3f7ad3a0be…58de3b
Audit this contract →
← previous block·next block →recent activity