pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,284,361
← previous block
next block →
recent activity
Analyzing
Block #74,284,361
9 transactions · 7 stateful · 2026-05-13 08:29:15 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,284,361
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x6a0436d3
#4
0xed82b078
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#2
0x0c7abd22
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
0x14ed2c47…ca6f
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2f5db56d…87b5
0x065c9d…c394
2 touches
0 conflicts
0xa7fb6a0a…8bc7
0x065c9d…c394
2 touches
0 conflicts
0xa7fb6a0a…8bc8
0x065c9d…c394
2 touches
0 conflicts
0xb08fd573…f458
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:
0xd32edf66…9fff58
1 conflict on slot
0x14ed2c4755…d7ca6f
Audit this contract →
← previous block
·
next block →
recent activity