pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,097,813
← previous block
next block →
recent activity
Analyzing
Block #75,097,813
10 transactions · 9 stateful · 2026-05-17 03:01:08 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,097,813
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe7be4706
#2
0x98717539
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xe7be4706
#5
0x5339c59f
#6
0x5339c59f
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x11f25e19…8bb1
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x62d6e82b…a750
0x34b655…2a6f
2 touches
0 conflicts
0x9b36f19f…fa5a
0x34b655…2a6f
2 touches
0 conflicts
0xc0f0c4dd…0e39
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:
0x34b6552d…112a6f
1 conflict on slot
0xb9868b5233…c6c77f
Audit this contract →
← previous block
·
next block →
recent activity