pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,617,935
← previous block
next block →
recent activity
Analyzing
Block #84,617,935
8 transactions · 6 stateful · 2026-06-30 05:32:22 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,617,935
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x5bf9264c
· blocks 1
#5
0x0f6795d9
#6
setData
#7
0x39435dac
#4
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x170e4e4c…2b90
0x34b655…2a6f
2 touches
0 conflicts
0x2bedbb62…a662
0x34b655…2a6f
2 touches
0 conflicts
0x40b5f387…a164
0x34b655…2a6f
2 touches
0 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
2 touches
0 conflicts
0xa16b3e4e…0787
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
0xe5bb3628b5…71e5e8
Audit this contract →
← previous block
·
next block →
recent activity