pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,284,622
← previous block
next block →
recent activity
Analyzing
Block #74,284,622
8 transactions · 6 stateful · 2026-05-13 08:31:00 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,284,622
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
0x39435dac
· blocks 1
#4
collect
#5
0xa09e9040
#6
setData
#7
0x39435dac
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbb571e4…6829
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x07a7a2f2…754f
0x065c9d…c394
2 touches
0 conflicts
0xd473355f…85f9
0x065c9d…c394
2 touches
0 conflicts
0xfb083229…0138
0x2a68ba…90c5
2 touches
0 conflicts
0x2fad73a1…ae09
0x34b655…2a6f
2 touches
0 conflicts
0x367dd22b…8f55
0x34b655…2a6f
2 touches
0 conflicts
0x41f84c6d…8369
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:
Perpl
1 conflict on slot
0xdbb571e456…b26829
Audit this contract →
← previous block
·
next block →
recent activity