pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,025,694
← previous block
next block →
recent activity
Analyzing
Block #84,025,694
11 transactions · 7 stateful · 2026-06-27 11:45:20 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,025,694
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x98717539
· blocks 1
#4
0x0f6795d9
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
0xe5bd42…88ae
#8
0x3d96d2…26fd
#9
setData
#10
0x39435dac
#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
0xb3975d93…b4a2
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x0020cef4…3ffc
0x34b655…2a6f
2 touches
0 conflicts
0x4558aa66…592e
0x34b655…2a6f
2 touches
0 conflicts
0x5643c292…b314
0x34b655…2a6f
2 touches
0 conflicts
0x58f3a843…9ac2
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
0xb3975d9364…28b4a2
Audit this contract →
← previous block
·
next block →
recent activity