pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,283,432
← previous block
next block →
recent activity
Analyzing
Block #74,283,432
8 transactions · 8 stateful · 2026-05-13 08:23:04 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,283,432
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updateDataFeedsValuesPartial
#3
setData
#5
0x6a04355f
#6
0x39435dac
· blocks 1
#4
0x42bbae7a
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x23a320fb…cbd7
0x34b655…2a6f
4 touches
1 conflict
0xcfe99fc9…93ba
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x23b76127…ac5d
0x065c9d…c394
2 touches
0 conflicts
0x3c62f198…565d
0x065c9d…c394
2 touches
0 conflicts
0x3e2ba7e2…ac6a
0x065c9d…c394
2 touches
0 conflicts
0x7d8252a0…ff3b
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xc3c8642ae9…317da5
Audit this contract →
← previous block
·
next block →
recent activity