pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,528,477
← previous block
next block →
recent activity
Analyzing
Block #75,528,477
8 transactions · 5 stateful · 2026-05-19 03:06:56 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,528,477
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#4
0x5339c59f
#5
setData
#6
0xba0897…41a0
#7
0x68811f…0835
#3
0x5339c59f
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
0x068be977…2291
0x065c9d…c394
4 touches
1 conflict
0x51855398…4229
0x065c9d…c394
3 touches
1 conflict
0x9bd0b62f…001b
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0f92c085…7a22
0x065c9d…c394
2 touches
0 conflicts
0x543ecc03…1730
0x065c9d…c394
2 touches
0 conflicts
0x56fdf2e4…1295
0x065c9d…c394
2 touches
0 conflicts
0x7e75e0e3…cb56
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
0x068be977f4…5c2291
Audit this contract →
← previous block
·
next block →
recent activity