pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,465,983
← previous block
next block →
recent activity
Analyzing
Block #74,465,983
10 transactions · 4 stateful · 2026-05-14 04:37:56 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,465,983
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
flash
· blocks 1
#2
0x506c9c…c257
#4
0x39435dac
#5
updateDataFeedsValuesPartial
#6
0x96489a…f12d
#7
0xfc5c98…9429
#8
0xdd2c81…e531
#9
setData
#3
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x1252da2c…1e9a
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x354d92…66fb
2 touches
0 conflicts
0x00000000…0001
0x354d92…66fb
2 touches
0 conflicts
0x00000000…0005
0x354d92…66fb
2 touches
0 conflicts
0xe90b7bce…c2e0
0x354d92…66fb
2 touches
0 conflicts
0xa980598e…ec52
0x3bd359…433a
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity