pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,631,485
← previous block
next block →
recent activity
Analyzing
Block #74,631,485
9 transactions · 8 stateful · 2026-05-14 23:07:15 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,631,485
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
swap
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x39435dac
· blocks 1
#6
0x6a06561b
#7
setData
#5
0xed82b078
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xef22fc15…bd08
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x037849a8…fa88
0x34b655…2a6f
2 touches
0 conflicts
0x037849a8…fa8d
0x34b655…2a6f
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: Market-MON/USDC
1 conflict on slot
0xffe431af56…838faa
Audit this contract →
← previous block
·
next block →
recent activity