pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#71,329,711
← previous block
next block →
recent activity
Analyzing
Block #71,329,711
10 transactions · 9 stateful · 2026-04-29 16:08:04 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,329,711
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1a945f9c
· blocks 1
#3
0x0c7abd22
#4
updateDataFeedsValuesPartial
#5
setData
#6
execOrders
#7
execOrders
#8
execOrders
#9
execOrders
#2
0x366fe5db
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
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5f53a383…ac9b
0x1efe02…37d6
2 touches
0 conflicts
0x1728ed63…499c
0xea1b8e…c5ec
2 touches
0 conflicts
0x3d7a5755…46ba
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0x9c8d6dd6…d619
0xea1b8e…c5ec
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:
0xfd44b351…7f00d1
1 conflict on slot
0x00bac0131a…bba28c
Audit this contract →
← previous block
·
next block →
recent activity