pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,456,252
← previous block
next block →
recent activity
Analyzing
Block #74,456,252
9 transactions · 8 stateful · 2026-05-14 03:33:09 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,456,252
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x98717539
#4
setData
#5
redeemDelegations
· blocks 1
#7
0x6a0542ed
#8
markGameAsLost
#6
redeemDelegations
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
0x00000000…0000
0x6cfe51…4fdc
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x06099e49…502e
0x34b655…2a6f
2 touches
0 conflicts
0x0bbe6742…e34a
0x34b655…2a6f
2 touches
0 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x2362c85a…df78
0x34b655…2a6f
2 touches
0 conflicts
0x2fad73a1…ae09
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:
0x6cfe5187…454fdc
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity