pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,523,819
← previous block
next block →
recent activity
Analyzing
Block #76,523,819
11 transactions · 9 stateful · 2026-05-23 17:38:29 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,523,819
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5339c59f
· blocks 1
#2
0x98717539
#4
updateDataFeedsValuesPartial
#5
artefact_keep
#6
redeemDelegations
#7
0x0f6795d9
#8
0x0f6795d9
#9
setData
#10
0x0f6795d9
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1143e1d6…5289
0x065c9d…c394
2 touches
0 conflicts
0x95523e2a…4c01
0x065c9d…c394
2 touches
0 conflicts
0x22e81583…6d62
0x34b655…2a6f
2 touches
0 conflicts
0x28e82642…efa7
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: MarginAccount
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity