pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,504,550
← previous block
next block →
recent activity
Analyzing
Block #74,504,550
10 transactions · 10 stateful · 2026-05-14 08:54:45 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,504,550
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
0x98717539
#3
0x6df9e92b
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
swapExactIn
· blocks 1
#9
0x39435dac
#4
0x6df9e92b
#8
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xcc67aa…c71c
4 touches
1 conflict
0x2d603f45…1c6f
0x699abc…6a3b
4 touches
1 conflict
0xe0b1fab4…b85c
0x699abc…6a3b
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xb0f4dbcb…926a
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xcc67aa…c71c
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0xe069120c…952c
0x000000…012a
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:
0xcc67aab1…cac71c
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity