pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,124,625
← previous block
next block →
recent activity
Analyzing
Block #75,124,625
9 transactions · 7 stateful · 2026-05-17 06:00:05 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,124,625
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
artefact_keep
#2
0x6df9e92b
#3
0xed82b078
#4
updateDataFeedsValuesPartial
#5
0xe9316489
#6
setData
#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
0x8a5efe9a…fa31
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x44ad89ba…cf83
0x0a917f…7777
2 touches
0 conflicts
0x8fa7a69c…8fd7
0x0a917f…7777
2 touches
0 conflicts
0x00000000…0004
0x23035f…7992
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:
0x34b6552d…112a6f
1 conflict on slot
0x8a5efe9a05…effa31
Audit this contract →
← previous block
·
next block →
recent activity