pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,905,934
← previous block
next block →
recent activity
Analyzing
Block #74,905,934
10 transactions · 8 stateful · 2026-05-16 05:38:56 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,905,934
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
0x98717539
#6
0x6a080368
#7
setData
#8
0x4b1a75…3d74
#9
0x39435dac
#2
_makeSwaps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0xce2b5de0…b57f
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5df51046…d4a8
0x065c9d…c394
2 touches
0 conflicts
0x72720b95…2d14
0x065c9d…c394
2 touches
0 conflicts
0xa5baba98…8dc7
0x065c9d…c394
2 touches
0 conflicts
0xbde5a0e3…927c
0x065c9d…c394
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
0x30276c1c08…7247b4
Audit this contract →
← previous block
·
next block →
recent activity