pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,598,803
← previous block
next block →
recent activity
Analyzing
Block #74,598,803
10 transactions · 7 stateful · 2026-05-14 19:28:54 UTC
Parallelism
80
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,598,803
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x05ee6a22
· blocks 1
#3
updatePrices
· blocks 1
#5
setData
#6
0xed82b078
#7
0x6a0622ee
#8
0x314e08…8193
#9
0x0bf342…db59
#2
removeLiquidity
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xc5819118…1448
0x39f901…6bdf
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0xbfe7fd3a…3168
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x4e8aae…4298
2 touches
0 conflicts
0x5ded6b55…161e
0x4e8aae…4298
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:
0x5afd3ec8…e77620
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity