pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,487,549
← previous block
next block →
recent activity
Analyzing
Block #74,487,549
7 transactions · 5 stateful · 2026-05-14 07:01:22 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,487,549
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
0x98717539
· blocks 1
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x56ff7a…b401
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62d080e9…4a7c
0x34b655…2a6f
4 touches
1 conflict
0x355ce8fd…2b3d
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0aaee5aa…0940
0x065c9d…c394
2 touches
0 conflicts
0x239cb587…80a4
0x065c9d…c394
2 touches
0 conflicts
0x8ba17998…fbaa
0x065c9d…c394
2 touches
0 conflicts
0xfb81cde7…4958
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:
0x34b6552d…112a6f
1 conflict on slot
0x62d080e928…5a4a7c
Audit this contract →
← previous block
·
next block →
recent activity