← previous blocknext block →recent activity
Analyzing
Block #84,077,629
21 transactions · 16 stateful · 2026-06-27 17:31:12 UTC
Parallelism
90/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,077,629 · 21 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
4w05w18w011w012w013w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x482e79aa…6aad
0xd32edf…ff58
3 touches
1 conflict
0x62d6e82b…a750
0x34b655…2a6f
2 touches
0 conflicts
0x66e47d07…baa6
0x34b655…2a6f
2 touches
0 conflicts
0x97f5b001…24db
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 0xbd68c7c758…bd40b3
Audit this contract →
← previous block·next block →recent activity