pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,171,099
← previous block
next block →
recent activity
Analyzing
Block #73,171,099
10 transactions · 9 stateful · 2026-05-08 04:42:44 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,171,099
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0x69fd6a3c
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
forward
#8
0xeffdedb0
#9
setData
#2
0xbc3ec4c2
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x27fcc0ea…7ee3
0x065c9d…c394
2 touches
0 conflicts
0x2a354a63…0515
0x065c9d…c394
2 touches
0 conflicts
0x2f9e01e1…e43e
0x065c9d…c394
2 touches
0 conflicts
0x8e66da19…66b6
0x065c9d…c394
2 touches
0 conflicts
0x00000000…000d
0x1b6862…e19c
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: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity