pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,444,291
← previous block
next block →
recent activity
Analyzing
Block #76,444,291
15 transactions · 12 stateful · 2026-05-23 08:48:58 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,444,291
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5339c59f
· blocks 1
#2
0x5339c59f
#3
execute
#4
multicall
#6
updateDataFeedsValuesPartial
#7
redeemDelegations
#8
0x0f6795d9
#9
0x0f6795d9
#10
0xc5918880
#11
forward
#12
forward
#13
0xe8891658
#14
setData
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
2 touches
0 conflicts
0xc1622b40…9cd3
0x46a15b…4364
2 touches
0 conflicts
0xc1622b40…9cd4
0x46a15b…4364
2 touches
0 conflicts
0xc1622b40…9cd5
0x46a15b…4364
2 touches
0 conflicts
0x22a828bf…8b10
0x5e0734…69c1
2 touches
0 conflicts
0x39754d3c…2410
0x5e0734…69c1
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity