pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,936,574
← previous block
next block →
recent activity
Analyzing
Block #75,936,574
10 transactions · 6 stateful · 2026-05-21 00:27:28 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,936,574
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
0x5339c59f
#7
setData
#9
0x39435dac
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0462262d…a368
0x34b655…2a6f
2 touches
0 conflicts
0x167f697f…7f61
0x34b655…2a6f
2 touches
0 conflicts
0x167f697f…7f62
0x34b655…2a6f
2 touches
0 conflicts
0x167f697f…7f66
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:
Perpl
1 conflict on slot
0x310a7246ab…012dcb
Audit this contract →
← previous block
·
next block →
recent activity