pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,485,403
← previous block
next block →
recent activity
Analyzing
Block #74,485,403
8 transactions · 7 stateful · 2026-05-14 06:47:05 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,485,403
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
redeemDelegations
· blocks 1
#5
0x39435dac
· blocks 1
#7
0x39435dac
#4
redeemDelegations
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xd7afba…d86a
4 touches
1 conflict
0x0b6d25a1…2e3b
0x34b655…2a6f
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
4 touches
1 conflict
0x4b90cfff…b2b3
0x34b655…2a6f
4 touches
1 conflict
0x7cee1be1…e770
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
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:
0xd7afba3d…e7d86a
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity