← previous blocknext block →recent activity
Analyzing
Block #84,035,935
24 transactions · 18 stateful · 2026-06-27 12:53:29 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,035,935 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w311w013w014w118w421w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93d680fb…ac21
0x34b655…2a6f
8 touches
6 conflicts
0x63793865…0cf7
0xd32edf…ff58
7 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x77dc4958…659e
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x93afca4c…b47b
0x1b6862…e19c
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 0x93d680fb3b…fdac21
Audit this contract →
← previous block·next block →recent activity