pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,310,998
← previous block
next block →
recent activity
Analyzing
Block #72,310,998
10 transactions · 6 stateful · 2026-05-04 05:14:13 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,310,998
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe7be4706
#2
0xe7be4706
#3
0xe2dc7dc3
#4
updateDataFeedsValuesPartial
#5
0xe7be4706
#6
0x3f5c179b
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7b7bcac3…8fbf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x3f847af7…d491
0x1efe02…37d6
2 touches
0 conflicts
0x5c04a735…023f
0x1efe02…37d6
2 touches
0 conflicts
0x6ac391ef…a135
0x1efe02…37d6
2 touches
0 conflicts
0x99836eb9…87a3
0x1efe02…37d6
2 touches
0 conflicts
0xb8a0b1ac…1f03
0x1efe02…37d6
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity