← previous blocknext block →recent activity
Analyzing
Block #84,185,336
16 transactions · 14 stateful · 2026-06-28 05:28:23 UTC
Parallelism
81/100
Blocked
14%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,185,336 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w08w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16f34741…5dee
0x34b655…2a6f
6 touches
3 conflicts
0xf00c4f4c…6228
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
0x34b655…2a6f
4 touches
1 conflict
0x9694aac3…b4d3
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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 0x16f3474156…815dee
Audit this contract →
← previous block·next block →recent activity