← previous blocknext block →recent activity
Analyzing
Block #84,200,839
16 transactions · 15 stateful · 2026-06-28 07:11:39 UTC
Parallelism
50/100
Blocked
47%
Avg conflicts / tx
1.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,200,839 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf195ad96…e0c3
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…00c9
0x34b655…2a6f
16 touches
28 conflicts
0x252771a6…3918
0x34b655…2a6f
16 touches
28 conflicts
0x64db8826…ac87
0x34b655…2a6f
16 touches
28 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
16 touches
28 conflicts
0x8a7af3fd…72a6
0x34b655…2a6f
16 touches
28 conflicts
0xb45b8528…8be1
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…641f
0x34b655…2a6f
16 touches
28 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
28 conflicts on slot 0xf195ad96b6…00e0c3
Audit this contract →
← previous block·next block →recent activity