pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,951,275
← previous block
next block →
recent activity
Analyzing
Block #83,951,275
9 transactions · 7 stateful · 2026-06-27 03:29:31 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,951,275
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x0f6795d9
· blocks 1
#4
0xed82b078
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
0x6a3f4413
#8
setData
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x90a9e3f8…17ab
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x103e429e…066b
0x34b655…2a6f
2 touches
0 conflicts
0x1081406b…afe2
0x34b655…2a6f
2 touches
0 conflicts
0x16c6549d…b016
0x34b655…2a6f
2 touches
0 conflicts
0x17ac66cd…84a8
0x34b655…2a6f
2 touches
0 conflicts
0x18addb73…ef6c
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
0x4f4bdabdf3…ecffba
Audit this contract →
← previous block
·
next block →
recent activity