pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,968,737
← previous block
next block →
recent activity
Analyzing
Block #73,968,737
9 transactions · 6 stateful · 2026-05-11 21:27:07 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,968,737
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 1
#2
execute
#3
0x4d8dc985
#4
approve
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x402da7db…cde4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe197f389…2648
0x065c9d…c394
3 touches
1 conflict
0x184229dc…04fc
0x065c9d…c394
2 touches
0 conflicts
0x18bf5f12…1099
0x065c9d…c394
2 touches
0 conflicts
0x2601e33f…5569
0x065c9d…c394
2 touches
0 conflicts
0xadb7bd5a…b71e
0x065c9d…c394
2 touches
0 conflicts
0xb9177109…0a99
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:
0x065c9d28…a9c394
1 conflict on slot
0x402da7db29…c3cde4
Audit this contract →
← previous block
·
next block →
recent activity