pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,416,843
← previous block
next block →
recent activity
Analyzing
Block #73,416,843
9 transactions · 8 stateful · 2026-05-09 07:58:04 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,416,843
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x121eab2f
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x5339c59f
· blocks 2
#6
0x69fee983
#7
0xeffdedb0
#8
setData
#4
0x5339c59f
· blocks 1
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x666edeee…64d6
0x065c9d…c394
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xa31478ea…3421
0x065c9d…c394
3 touches
1 conflict
0xad02aee5…a093
0x065c9d…c394
3 touches
1 conflict
0x4176d97f…5611
0x065c9d…c394
2 touches
0 conflicts
0x48d1799c…a777
0x065c9d…c394
2 touches
0 conflicts
0x56b3c9c7…7783
0x065c9d…c394
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
3 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity