← previous blocknext block →recent activity
Analyzing
Block #84,558,586
30 transactions · 22 stateful · 2026-06-29 22:56:48 UTC
Parallelism
87/100
Blocked
50%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,558,586 · 30 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
1w04w05w112w013w114w117w018w019w120w222w123w224w325w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74888025…a5b8
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64dc
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x02c4bb0f…f2c8
0x34b655…2a6f
6 touches
3 conflicts
0x6e942750…9953
0x34b655…2a6f
5 touches
3 conflicts
0x56253387…ff0e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0x74888025b0…84a5b8
Audit this contract →
← previous block·next block →recent activity