pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,349,834
← previous block
next block →
recent activity
Analyzing
Block #84,349,834
10 transactions · 9 stateful · 2026-06-28 23:44:28 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,349,834
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x98717539
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
0x6a41b254
#7
setData
#8
0x39435dac
#9
0xc7e3ec2c
#4
0x0f6795d9
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
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x5e374775…336c
0x34b655…2a6f
4 touches
1 conflict
0x04281002…5867
0x34b655…2a6f
2 touches
0 conflicts
0x0b56d384…2178
0x34b655…2a6f
2 touches
0 conflicts
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x24ea1541…724e
0x34b655…2a6f
2 touches
0 conflicts
0x2754e960…bcc1
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
0x89999c1534…effdac
Audit this contract →
← previous block
·
next block →
recent activity