pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,987,025
10 transactions · 6 stateful · 2026-05-11 23:29:56 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,987,025 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x467e3587…92cb
0x065c9d…c394
2 touches
0 conflicts
0x5877fb10…bde9
0x065c9d…c394
2 touches
0 conflicts
0x73a73cbe…84b0
0x065c9d…c394
2 touches
0 conflicts
0xb7810a8b…1221
0x065c9d…c394
2 touches
0 conflicts
0xcf5cff9b…7a6a
0x065c9d…c394
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: 0x065c9d28…a9c394
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity