pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,970,500
← previous block
next block →
recent activity
Analyzing
Block #73,970,500
8 transactions · 7 stateful · 2026-05-11 21:38:54 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,970,500
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 2
#2
setData
#3
mintCube
#5
updateDataFeedsValuesPartial
#7
transfer
#4
0x0c7abd22
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xef44ee6b…2baa
0x065c9d…c394
4 touches
1 conflict
0x25fc054d…2c3f
0x065c9d…c394
3 touches
1 conflict
0x3a492f97…b78e
0x065c9d…c394
3 touches
1 conflict
0xf537eaa0…73c8
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x1195cf…64b7
2 touches
0 conflicts
0x39ef8db1…e653
0x1195cf…64b7
2 touches
0 conflicts
0x6e541651…b5e8
0x1195cf…64b7
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity