pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,090,336
← previous block
next block →
recent activity
Analyzing
Block #76,090,336
13 transactions · 8 stateful · 2026-05-21 17:32:00 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,090,336
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x0f6795d9
#6
0x6df9e92b
· blocks 1
#8
0x6df9e92b
#9
0x32cd9d…d761
#10
withdraw
#11
setData
#12
0x39435dac
#7
0x6df9e92b
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
0x6ac11407…0bcc
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0xd10cf1…7777
4 touches
1 conflict
0x5180f24b…0b96
0xd10cf1…7777
4 touches
1 conflict
0x00000000…0000
0xd57e82…8ed4
4 touches
1 conflict
0x00000000…0001
0xd57e82…8ed4
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
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:
Wrapped MON (WMON)
1 conflict on slot
0x6ac1140747…b80bcc
Audit this contract →
← previous block
·
next block →
recent activity