pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,186,875
← previous block
next block →
recent activity
Analyzing
Block #84,186,875
10 transactions · 8 stateful · 2026-06-28 05:38:37 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,186,875
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
0x0c7abd22
#5
0xed82b078
#6
0x39435dac
#8
updateDataFeedsValuesPartial
#9
setData
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xa4994f59…060c
0x34b655…2a6f
4 touches
1 conflict
0x17ad8913…0339
0x34b655…2a6f
4 touches
1 conflict
0x2b6da52b…69cf
0x34b655…2a6f
4 touches
1 conflict
0x3adb0a2b…69ab
0x34b655…2a6f
4 touches
1 conflict
0x1924805b…b889
0x40c49f…2af0
2 touches
0 conflicts
0x67c5ab85…b0e9
0x40c49f…2af0
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
0x6f132c01d5…7dcdcc
Audit this contract →
← previous block
·
next block →
recent activity