← previous blocknext block →recent activity
Analyzing
Block #84,461,706
30 transactions · 25 stateful · 2026-06-29 12:10:10 UTC
Parallelism
80/100
Blocked
60%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,461,706 · 30 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
3w05w17w08w19w210w011w114w015w116w217w318w119w420w222w126w327w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77dc4958…659e
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x93d680fb…ac21
0x34b655…2a6f
6 touches
3 conflicts
0x9540632c…78a0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x942a422e…c250
0x34b655…2a6f
4 touches
1 conflict
0x2d5c395b…6b5a
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
10 conflicts on slot 0x77dc495815…97659e
Audit this contract →
← previous block·next block →recent activity