pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,615,224
← previous block
next block →
recent activity
Analyzing
Block #84,615,224
6 transactions · 4 stateful · 2026-06-30 05:14:21 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,615,224
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x39435dac
· blocks 1
#3
0x0f6795d9
· blocks 1
#4
setData
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97fe3267…5e87
0x34b655…2a6f
4 touches
1 conflict
0xcfe15fba…4f97
0x34b655…2a6f
4 touches
1 conflict
0xdcf90674…5bf6
0x34b655…2a6f
4 touches
1 conflict
0x1ca5aec6…c1e1
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x24227bc5…cb16
0x34b655…2a6f
2 touches
0 conflicts
0x274b85f7…c526
0x34b655…2a6f
2 touches
0 conflicts
0x2b654f1e…a9b1
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
0x97fe32673b…cb5e87
Audit this contract →
← previous block
·
next block →
recent activity