← previous blocknext block →recent activity
Analyzing
Block #84,075,713
25 transactions · 22 stateful · 2026-06-27 17:18:25 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,075,713 · 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
4w05w18w09w010w111w112w213w314w415w417w118w120w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb30e1191…9e3c
0x34b655…2a6f
8 touches
6 conflicts
0x29686688…0598
0xa6afd3…d132
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xf65e878a…c43c
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x0c969dde…6b06
0xa6afd3…d132
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 0xb30e119129…4f9e3c
Audit this contract →
← previous block·next block →recent activity