pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,161,715
← previous block
next block →
recent activity
Analyzing
Block #73,161,715
8 transactions · 8 stateful · 2026-05-08 03:40:18 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,161,715
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x1a945f9c
· blocks 1
#3
updateDataFeedsValuesPartial
#5
0x69fd5b9a
#6
0xeffdedb0
#7
setData
#4
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0xf414c802…6b27
0xfd44b3…00d1
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x7f189cf6…afab
0x065c9d…c394
2 touches
0 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
2 touches
0 conflicts
0xd09004cb…5088
0x065c9d…c394
2 touches
0 conflicts
0xd60000a2…3de1
0x065c9d…c394
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:
0xfd44b351…7f00d1
1 conflict on slot
0x00bac0131a…bba28c
Audit this contract →
← previous block
·
next block →
recent activity