pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,257,565
← previous block
next block →
recent activity
Analyzing
Block #74,257,565
8 transactions · 5 stateful · 2026-05-13 05:31:05 UTC
Parallelism
75
/100
Blocked
40
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,257,565
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a040d11
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x39435dac
#5
0x39435dac
· blocks 2
#6
0x39435dac
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1630ed91…9774
0x34b655…2a6f
2 touches
0 conflicts
0x37674bd8…8f35
0x34b655…2a6f
2 touches
0 conflicts
0x37cfaf01…4a46
0x34b655…2a6f
2 touches
0 conflicts
0x43654310…a42d
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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:
0x34b6552d…112a6f
1 conflict on slot
0x4f4bdabdf3…ecffba
Audit this contract →
← previous block
·
next block →
recent activity