pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,899,646
← previous block
next block →
recent activity
Analyzing
Block #74,899,646
7 transactions · 7 stateful · 2026-05-16 04:57:00 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,899,646
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x323fe4ce
#2
updateDataFeedsValuesPartial
#3
0x6a07f994
#4
setData
#5
0x39435dac
· blocks 1
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea57afd0…4232
0x34b655…2a6f
4 touches
1 conflict
0xc7f28b7a…5777
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x064b2183…071a
0xea1b8e…c5ec
2 touches
0 conflicts
0x1c1a981e…f3da
0xea1b8e…c5ec
2 touches
0 conflicts
0x3572bd92…dd29
0xea1b8e…c5ec
2 touches
0 conflicts
0x3694f0c3…6b8c
0xea1b8e…c5ec
2 touches
0 conflicts
0x36f6824c…700a
0xea1b8e…c5ec
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
0xea57afd097…7f4232
Audit this contract →
← previous block
·
next block →
recent activity