pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,327,696
← previous block
next block →
recent activity
Analyzing
Block #84,327,696
10 transactions · 7 stateful · 2026-06-28 21:16:59 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,327,696
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x98717539
#4
poke
#5
0x98717539
#6
0x85367786
· blocks 1
#8
0x6b1a20…233b
#9
0xe27419…1695
#7
0x85367786
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0016
0x8fbe07…71b6
4 touches
1 conflict
0x0494780e…2900
0x8fbe07…71b6
4 touches
1 conflict
0xa6fd7409…16b7
0x8fbe07…71b6
4 touches
1 conflict
0x5ebb19ec…ce9a
0xdde003…c9a4
4 touches
1 conflict
0xb983f9fc…9b91
0xdde003…c9a4
4 touches
1 conflict
0x6ddff1a7…4560
0x34b655…2a6f
2 touches
0 conflicts
0x75194ada…a1c5
0x34b655…2a6f
2 touches
0 conflicts
0x7cb2f3fa…4836
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:
0x8fbe0741…fa71b6
1 conflict on slot
0x0000000000…000016
Audit this contract →
← previous block
·
next block →
recent activity