← previous blocknext block →recent activity
Analyzing
Block #84,306,830
7 transactions · 6 stateful · 2026-06-28 18:58:00 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,306,830 · 7 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
1w02w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ca68aab…5e4a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1b6e8fc2…73d4
0x34b655…2a6f
2 touches
0 conflicts
0x23ab8481…52d5
0x34b655…2a6f
2 touches
0 conflicts
0x2666137c…e4ea
0x34b655…2a6f
2 touches
0 conflicts
0x431f59a6…a342
0x34b655…2a6f
2 touches
0 conflicts
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 0x1ca68aab2e…3d5e4a
Audit this contract →
← previous block·next block →recent activity