← previous blocknext block →recent activity
Analyzing
Block #84,607,133
17 transactions · 16 stateful · 2026-06-30 04:20:28 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,607,133 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w110w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xa16b3e4e…0787
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x61cf51c7…a4ee
0x34b655…2a6f
2 touches
0 conflicts
0x666a6b8d…e563
0x34b655…2a6f
2 touches
0 conflicts
0x7bd91f28…50b3
0x34b655…2a6f
2 touches
0 conflicts
0x98d3fc79…df78
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xb3fb9fb561…7664dc
Audit this contract →
← previous block·next block →recent activity