pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,478,063
← previous block
next block →
recent activity
Analyzing
Block #73,478,063
9 transactions · 8 stateful · 2026-05-09 14:45:21 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,478,063
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98c6107a
· blocks 1
#3
0x98717539
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#2
0x98c6107a
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f430e47…4cbd
0x8d66a4…3095
4 touches
1 conflict
0x536e2740…61ac
0x3bd359…433a
4 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0x8fa7a69c…8fd7
0x4060a7…7777
4 touches
1 conflict
0x00000000…0002
0xa7283d…0ace
4 touches
1 conflict
0xfcf0ae2b…30ed
0xa7283d…0ace
4 touches
1 conflict
0xfcf0ae2b…30ee
0xa7283d…0ace
4 touches
1 conflict
0xfcf0ae2b…30ef
0xa7283d…0ace
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:
0x8d66a43f…113095
1 conflict on slot
0x7f430e471f…4e4cbd
Audit this contract →
← previous block
·
next block →
recent activity