← previous blocknext block →recent activity
Analyzing
Block #84,523,761
17 transactions · 15 stateful · 2026-06-29 19:04:10 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,523,761 · 17 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
5w06w17w28w39w412w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc94da5de…7ca7
0x34b655…2a6f
6 touches
3 conflicts
0x019ded9d…6fa0
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x58c659ec…3c6c
0x34b655…2a6f
4 touches
1 conflict
0x60934524…4fc5
0x34b655…2a6f
4 touches
1 conflict
0x67d8b378…f2f8
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
3 conflicts on slot 0xc94da5dede…d77ca7
Audit this contract →
← previous block·next block →recent activity