pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,229,064
← previous block
next block →
recent activity
Analyzing
Block #74,229,064
12 transactions · 8 stateful · 2026-05-13 02:21:37 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,229,064
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute_route
#3
execute_route
#4
execute_route
#5
0x719d975a
#6
updateDataFeedsValuesPartial
#7
0x39435dac
· blocks 1
#9
forward
#10
forward
#11
setData
#8
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0xc9b39579…408c
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x59a54ff4…d21b
0x34b655…2a6f
4 touches
1 conflict
0x71e96b74…abe9
0x34b655…2a6f
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
2 touches
0 conflicts
0x99f666e3…b2a2
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:
Perpl
1 conflict on slot
0x768cffcdb0…d12648
Audit this contract →
← previous block
·
next block →
recent activity