pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,023,528
← previous block
next block →
recent activity
Analyzing
Block #74,023,528
10 transactions · 7 stateful · 2026-05-12 03:34:24 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,023,528
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x1ffa3c9b
· blocks 1
#3
0x785f5745
#4
updateDataFeedsValuesPartial
#6
execOrders
#7
forward
#8
0x6a02a038
#9
setData
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfe1414c4…bc38
0x065c9d…c394
3 touches
1 conflict
0x2f318a7e…401b
0x065c9d…c394
2 touches
0 conflicts
0x3f478af2…1a8b
0x065c9d…c394
2 touches
0 conflicts
0x54e891d0…22de
0x065c9d…c394
2 touches
0 conflicts
0xe21e89a2…c0d1
0x065c9d…c394
2 touches
0 conflicts
0x490911cc…5fea
0x0c65a0…0852
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