← previous blocknext block →recent activity
Analyzing
Block #84,461,999
24 transactions · 18 stateful · 2026-06-29 12:12:08 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,461,999 · 24 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
1w02w13w04w19w010w111w212w018w119w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18ca6535…87c1
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x0354e10e…85c8
0x34b655…2a6f
4 touches
1 conflict
0x24227bc5…cb16
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x9a5244ed…fc88
0x34b655…2a6f
4 touches
1 conflict
0x9f715341…353a
0x34b655…2a6f
4 touches
1 conflict
0xce337fa8…bffd
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 0x18ca65353a…1c87c1
Audit this contract →
← previous block·next block →recent activity