← previous blocknext block →recent activity
Analyzing
Block #84,304,072
14 transactions · 10 stateful · 2026-06-28 18:39:34 UTC
Parallelism
86/100
Blocked
30%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,304,072 · 14 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
2w05w08w010w111w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0x99c320a0…b4a8
0x34b655…2a6f
4 touches
1 conflict
0x0d1f04b9…eac5
0x065c9d…c394
4 touches
1 conflict
0x0f3b22bf…e574
0x34b655…2a6f
4 touches
1 conflict
0x1b015327…7b67
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xc6818e19…dbc1
0x065c9d…c394
3 touches
1 conflict
0x4d0728bd…4664
0x065c9d…c394
3 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
1 conflict on slot 0xab86573c9c…f3682e
Audit this contract →
← previous block·next block →recent activity