pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,194,423
← previous block
next block →
recent activity
Analyzing
Block #84,194,423
13 transactions · 12 stateful · 2026-06-28 06:28:51 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,194,423
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0d484c28
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
0x98717539
#7
0x0f6795d9
#8
0x4d8dc985
#9
forward
#10
0x6a40bf9b
#11
setData
#12
0x39435dac
#2
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x86212bc8…5d96
0x40c49f…2af0
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2c7e7448…9500
0x0000a8…8888
2 touches
0 conflicts
0x2c7e7448…9501
0x0000a8…8888
2 touches
0 conflicts
0x5cbdceef…85ac
0x0000a8…8888
2 touches
0 conflicts
0x92339d95…0801
0x0000a8…8888
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity