pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,842,547
← previous block
next block →
recent activity
Analyzing
Block #75,842,547
12 transactions · 8 stateful · 2026-05-20 14:00:37 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,842,547
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x6a0dbefd
#3
0x0f6795d9
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#8
0x5339c59f
#9
0xc3dc92…e388
#10
0xa815ff…7cb3
#11
setData
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x006e2dc6…ecf6
0x065c9d…c394
2 touches
0 conflicts
0x16252a52…3ffa
0x065c9d…c394
2 touches
0 conflicts
0x1bce278a…c43f
0x065c9d…c394
2 touches
0 conflicts
0x791358e5…5a01
0x065c9d…c394
2 touches
0 conflicts
0xa649dc5f…5f1f
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: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity