pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,183,784
← previous block
next block →
recent activity
Analyzing
Block #74,183,784
9 transactions · 8 stateful · 2026-05-12 21:20:32 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,183,784
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x39ecce49
· blocks 2
#4
0x1ffa3c9b
#5
forward
#6
updateDataFeedsValuesPartial
#7
0x6a039a18
#8
setData
#2
0x39ecce49
· blocks 1
#3
0x39ecce49
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47ad7b1e…421e
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0xe74a34…1df9
6 touches
3 conflicts
0x00000000…0002
0xe74a34…1df9
6 touches
3 conflicts
0x00000000…0003
0xe74a34…1df9
6 touches
3 conflicts
0x0775d31f…cbfa
0x11ea57…7777
6 touches
3 conflicts
0xaf0edb55…9e7a
0x065c9d…c394
2 touches
0 conflicts
0xc99494c4…b7cc
0x065c9d…c394
2 touches
0 conflicts
0xd454b8ad…d9a3
0x065c9d…c394
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:
0x3bd359c1…15433a
3 conflicts on slot
0x47ad7b1e81…e1421e
Audit this contract →
← previous block
·
next block →
recent activity