pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,254,624
← previous block
next block →
recent activity
Analyzing
Block #84,254,624
12 transactions · 10 stateful · 2026-06-28 13:10:07 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,254,624
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#4
0x0c7abd22
· blocks 1
#5
0x0f6795d9
#6
forward
#7
forward
#8
0xed82b078
#10
approve
#11
setData
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x019ded9d…6fa0
0x34b655…2a6f
2 touches
0 conflicts
0x0da5118e…56b5
0x34b655…2a6f
2 touches
0 conflicts
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x35eaf8bc…5d80
0x34b655…2a6f
2 touches
0 conflicts
0x3f40bdb1…a880
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:
0x40c49f17…d22af0
1 conflict on slot
0xdfc5f34630…0b7b42
Audit this contract →
← previous block
·
next block →
recent activity