← previous blocknext block →recent activity
Analyzing
Block #84,359,210
17 transactions · 17 stateful · 2026-06-29 00:47:04 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,359,210 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w19w113w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0f1ea2a…a95d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x37a276a3…673f
0x34b655…2a6f
6 touches
3 conflicts
0xda47a23d…57e3
0xa6afd3…d132
4 touches
1 conflict
0x1951ee47…540f
0x34b655…2a6f
4 touches
1 conflict
0x300f4d3b…e6e3
0x34b655…2a6f
4 touches
1 conflict
0x37773728…f3a4
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 0xe0f1ea2af5…48a95d
Audit this contract →
← previous block·next block →recent activity