pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,979,437
← previous block
next block →
recent activity
Analyzing
Block #73,979,437
10 transactions · 6 stateful · 2026-05-11 22:38:58 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,979,437
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x98717539
· blocks 1
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
0x6a025afa
#8
setData
#9
0x00a56c…2070
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x60a42a5e…9da2
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
2 touches
0 conflicts
0xbf71a26d…354c
0x34b655…2a6f
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:
0x34b6552d…112a6f
1 conflict on slot
0xe283e878f8…797262
Audit this contract →
← previous block
·
next block →
recent activity