← previous blocknext block →recent activity
Analyzing
Block #84,705,627
32 transactions · 22 stateful · 2026-06-30 15:16:47 UTC
Parallelism
88/100
Blocked
41%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,705,627 · 32 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
1w04w05w17w09w113w014w117w018w119w220w324w129w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d691210…341b
0x34b655…2a6f
8 touches
6 conflicts
0xa3230eb8…9295
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x4560e5a8…b741
0x34b655…2a6f
6 touches
3 conflicts
0x5ffabfdb…35d0
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb21e45f5…e5cb
0x065c9d…c394
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
6 conflicts on slot 0x8d69121037…43341b
Audit this contract →
← previous block·next block →recent activity