pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,391,563
← previous block
next block →
recent activity
Analyzing
Block #74,391,563
10 transactions · 6 stateful · 2026-05-13 20:22:28 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
#74,391,563
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaa0506cd
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
get_block_hash_257335279069929
#6
setData
#7
0x3d240a…b7b2
#8
0x39435dac
#9
0x39435dac
#2
0xaa0506cd
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
0x874eb960…3f69
0x1aac02…7777
4 touches
1 conflict
0x536e2740…61ac
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0xa7283d…0ace
4 touches
1 conflict
0x7b05f5bd…1251
0xa7283d…0ace
4 touches
1 conflict
0x7b05f5bd…1252
0xa7283d…0ace
4 touches
1 conflict
0x7b05f5bd…1253
0xa7283d…0ace
4 touches
1 conflict
0x7b05f5bd…1254
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:
0x1aac02ea…7f7777
1 conflict on slot
0x874eb960cd…ca3f69
Audit this contract →
← previous block
·
next block →
recent activity