pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,947,716
← previous block
next block →
recent activity
Analyzing
Block #75,947,716
9 transactions · 8 stateful · 2026-05-21 01:41:43 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,947,716
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0xa391f92f
#5
setData
#6
0xf7ec19…79e1
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x1da1c6cb…bb3f
0x34b655…2a6f
4 touches
1 conflict
0x33a84dc6…30f0
0x34b655…2a6f
4 touches
1 conflict
0x5684aadd…8d62
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0006
0x2acef0…d54e
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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
0xfe39a1f75c…758eb0
Audit this contract →
← previous block
·
next block →
recent activity