← previous blocknext block →recent activity
Analyzing
Block #84,461,039
33 transactions · 24 stateful · 2026-06-29 12:05:42 UTC
Parallelism
73/100
Blocked
67%
Avg conflicts / tx
1.61
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #84,461,039 · 33 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w314w015w118w119w120w221w322w423w524w625w726w827w329w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77dc4958…659e
0x34b655…2a6f
16 touches
28 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0xe1593d74…b99c
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xb3975d93…b4a2
0x34b655…2a6f
8 touches
6 conflicts
0x5643c292…b314
0x34b655…2a6f
6 touches
3 conflicts
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
28 conflicts on slot 0x77dc495815…97659e
Audit this contract →
← previous block·next block →recent activity