pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,338,358
← previous block
next block →
recent activity
Analyzing
Block #75,338,358
10 transactions · 9 stateful · 2026-05-18 05:48:43 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,338,358
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
#2
0x98717539
· blocks 1
#4
0xed82b078
#5
0x6df9e92b
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0x6a0aa8b2
#9
setData
#3
0x98717539
#6
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a2
0x8d66a4…3095
4 touches
1 conflict
0x44ad89ba…cf83
0x0cc9b2…7777
4 touches
1 conflict
0xa10c86f8…4b74
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x8a35acfb…d1a0
0x8d66a4…3095
4 touches
1 conflict
0x99a3a7c1…1e2b
0x0cc9b2…7777
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
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:
Perpl: Oracle / Operator Hub
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity