pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,354,734
← previous block
next block →
recent activity
Analyzing
Block #74,354,734
8 transactions · 7 stateful · 2026-05-13 16:17:21 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,354,734
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x6a04a488
#5
0x0e3593…8113
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0x250efed1…5a09
0x068f22…7908
2 touches
0 conflicts
0x48dab8e7…787a
0x068f22…7908
2 touches
0 conflicts
0x4d78c528…f88b
0x09475a…400f
2 touches
0 conflicts
0xee2e48fa…c427
0x09475a…400f
2 touches
0 conflicts
0x5eed8370…d27c
0x754704…b603
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:
0x34b6552d…112a6f
1 conflict on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity