pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,990,596
← previous block
next block →
recent activity
Analyzing
Block #73,990,596
10 transactions · 7 stateful · 2026-05-11 23:54:02 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,990,596
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
updateDataFeedsValuesPartial
#3
0x62be7533
#4
setData
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
#8
0x6a026c92
#9
0x39435dac
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fe4d51f…835a
0x34b655…2a6f
4 touches
1 conflict
0xbeb19f26…1530
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x6b7ebb7b…9f51
0x34b655…2a6f
4 touches
1 conflict
0x7dd1c9ce…5c0e
0x34b655…2a6f
4 touches
1 conflict
0x17232f94…9bb1
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
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
0x4fe4d51fb8…84835a
Audit this contract →
← previous block
·
next block →
recent activity