← previous blocknext block →recent activity
Analyzing
Block #84,514,734
22 transactions · 20 stateful · 2026-06-29 18:04:02 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,514,734 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w39w010w111w212w313w414w515w616w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0x6e2becf4…0c5f
0x34b655…2a6f
10 touches
10 conflicts
0x7c6d3d6d…9deb
0x34b655…2a6f
10 touches
10 conflicts
0x94710b77…a921
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xe4afaa2f…3b69
0xa6afd3…d132
6 touches
3 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity