pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,529,281
← previous block
next block →
recent activity
Analyzing
Block #74,529,281
13 transactions · 9 stateful · 2026-05-14 11:41:27 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,529,281
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapExactIn
#2
0x1ffa3c9b
#3
0x6a05b55e
#4
0x6df9e92b
· blocks 1
#6
updateDataFeedsValuesPartial
#7
batchUpdate
#8
approve
#9
setData
#10
0x059f2e…e8c2
#11
0x467d26…2937
#12
0x94f50c…c0f2
#5
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d1acd7c…f345
0x5e1b1a…7777
4 touches
1 conflict
0x5593214e…dfc1
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x75c3ab…4f0d
4 touches
1 conflict
0x00000000…0001
0x75c3ab…4f0d
4 touches
1 conflict
0x44ad89ba…cf83
0x5e1b1a…7777
4 touches
1 conflict
0x1a920eda…bfae
0x386489…7508
2 touches
0 conflicts
0x15bae5fc…9f7e
0x57ea24…2cec
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:
Chogi (CHOGI)
1 conflict on slot
0x4d1acd7cf0…b2f345
Audit this contract →
← previous block
·
next block →
recent activity