pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,187,566
← previous block
next block →
recent activity
Analyzing
Block #84,187,566
8 transactions · 8 stateful · 2026-06-28 05:43:14 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,187,566
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
0x0f6795d9
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e03ab9…ad5b
0x34b655…2a6f
4 touches
1 conflict
0x5cc8dd43…8cf2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x20e499f7…fa84
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x334b211a…dfd8
0x34b655…2a6f
2 touches
0 conflicts
0x4ff4520c…9343
0x34b655…2a6f
2 touches
0 conflicts
0x6f132c01…cdcc
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
0xb4e03ab93c…faad5b
Audit this contract →
← previous block
·
next block →
recent activity