pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,576,691
← previous block
next block →
recent activity
Analyzing
Block #72,576,691
8 transactions · 7 stateful · 2026-05-05 10:43:55 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,576,691
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
· blocks 1
#4
mintCube
#5
0xed82b078
#7
setData
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9110ddde…d701
0x065c9d…c394
4 touches
1 conflict
0xdb6fe0b8…baed
0x065c9d…c394
3 touches
1 conflict
0x2b397b26…724b
0x065c9d…c394
2 touches
0 conflicts
0x39f92eaf…1a20
0x065c9d…c394
2 touches
0 conflicts
0x648f19c5…34e1
0x065c9d…c394
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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