pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,514,164
← previous block
next block →
recent activity
Analyzing
Block #74,514,164
10 transactions · 10 stateful · 2026-05-14 09:59:33 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,514,164
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
deposit
#4
updateDataFeedsValuesPartial
#6
0x6a059d7c
#7
setData
#8
0x39435dac
· blocks 1
#3
0x42bbae7a
#5
0x5339c59f
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaeb5864c…7679
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0xb907285e…f866
0x40c49f…2af0
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x09beabbc…065d
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0xaeb5864c20…607679
Audit this contract →
← previous block
·
next block →
recent activity