pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,594,003
← previous block
next block →
recent activity
Analyzing
Block #74,594,003
10 transactions · 10 stateful · 2026-05-14 18:56:42 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,594,003
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
forward
#3
forward
#4
forward
#5
updateDataFeedsValuesPartial
#6
0x6a061b61
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0f9b918b…212d
0x34b655…2a6f
2 touches
0 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x1a8b5f50…63e4
0x34b655…2a6f
2 touches
0 conflicts
0x346d38f4…4da4
0x34b655…2a6f
2 touches
0 conflicts
0x5fbbfb42…a398
0x34b655…2a6f
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
0xa91c899f02…fa6ee3
Audit this contract →
← previous block
·
next block →
recent activity