← previous blocknext block →recent activity
Analyzing
Block #84,489,097
37 transactions · 32 stateful · 2026-06-29 15:12:55 UTC
Parallelism
73/100
Blocked
66%
Avg conflicts / tx
1.62
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #84,489,097 · 37 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w08w19w210w311w412w513w014w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xd637b3…4160
12 touches
15 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xac206e47…ef7d
0x34b655…2a6f
6 touches
3 conflicts
0x344dbdb0…0cc0
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity