← previous blocknext block →recent activity
Analyzing
Block #84,460,674
34 transactions · 24 stateful · 2026-06-29 12:03:16 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,460,674 · 34 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
1w05w06w17w29w010w117w018w120w021w122w023w124w227w231w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xd7e72076…294a
0x34b655…2a6f
6 touches
3 conflicts
0x1c3416ac…7c7e
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe4c6b0cb…0a23
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: Settlement / Helper
3 conflicts on slot 0xe02484a657…35c32e
Audit this contract →
← previous block·next block →recent activity