pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,610,656
← previous block
next block →
recent activity
Analyzing
Block #74,610,656
6 transactions · 5 stateful · 2026-05-14 20:48:24 UTC
Parallelism
67
/100
Blocked
40
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,610,656
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
updateDataFeedsValuesPartial
#5
setData
#2
0x0c7abd22
#3
0x719d975a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0xe5a8f8…d7a8
4 touches
1 conflict
0x67d47cb1…3fa2
0x188d58…ea8e
4 touches
1 conflict
0xbc467e7a…af36
0x21e325…7777
4 touches
1 conflict
0xd06cc746…27e4
0x21e325…7777
4 touches
1 conflict
0xae3fbd28…a18c
0x3bd359…433a
4 touches
1 conflict
0x67d47cb1…3fa0
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0000
0xe5a8f8…d7a8
4 touches
1 conflict
0x00000000…0001
0xe5a8f8…d7a8
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:
0xe5a8f88c…7dd7a8
1 conflict on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity