pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,042,605
← previous block
next block →
recent activity
Analyzing
Block #73,042,605
8 transactions · 6 stateful · 2026-05-07 14:28:04 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,042,605
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateIndexData
#3
0x6df9e92b
#4
relay
#5
setData
#6
execOrders
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0x1ee7a8f7…87f4
0x34b655…2a6f
2 touches
0 conflicts
0x536e2740…61ac
0x3bd359…433a
2 touches
0 conflicts
0xa472d565…9fe4
0x3bd359…433a
2 touches
0 conflicts
0x588e01f1…6a3a
0x3e4f2b…ba84
2 touches
0 conflicts
0x2bd6057a…370c
0x6f92c7…6a92
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
0xb91a6f59b9…c8722c
Audit this contract →
← previous block
·
next block →
recent activity