pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,677,554
← previous block
next block →
recent activity
Analyzing
Block #73,677,554
8 transactions · 7 stateful · 2026-05-10 12:57:09 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,677,554
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x98717539
· blocks 1
#7
0x39435dac
#2
0x1094dc9f
#6
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0xab3526…fa38
4 touches
1 conflict
0xdc7a27e1…d536
0x754704…b603
4 touches
1 conflict
0xe436ef16…99df
0x754704…b603
4 touches
1 conflict
0xfe49740d…4e57
0x754704…b603
4 touches
1 conflict
0x7f430e47…4cbd
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ab
0x8d66a4…3095
4 touches
1 conflict
0xaa04c44a…016e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0007
0x09f880…ede0
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity