pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,314,998
← previous block
next block →
recent activity
Analyzing
Block #72,314,998
8 transactions · 8 stateful · 2026-05-04 05:40:52 UTC
Parallelism
63
/100
Blocked
38
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,314,998
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0x3f5c179b
#6
updateDataFeedsValuesPartial
#7
setData
#2
execute
#4
createModule
· blocks 1
#5
0xa9b28aa6
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0xd025d7d7…f05a
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x46cb45de…a568
0x188d58…ea8e
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
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:
0x188d586d…f9ea8e
1 conflict on slot
0x46cb45de01…66a566
Audit this contract →
← previous block
·
next block →
recent activity