pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,478,700
26 transactions · 16 stateful · 2026-05-18 21:26:18 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,478,700 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w012w215w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0182bf94…8db5
0xd32edf…ff58
9 touches
10 conflicts
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x5dfa485c…cf52
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x9b60e5…f8ac
4 touches
1 conflict
0x00000000…0002
0x9b60e5…f8ac
4 touches
1 conflict
0x00000000…0004
0x9b60e5…f8ac
4 touches
1 conflict
0x37425495…d7f5
0xee8c0e…1242
4 touches
1 conflict
0xee0a9ebb…c425
0x0555e3…2b9c
4 touches
1 conflict
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: 0xd32edf66…9fff58
10 conflicts on slot 0x0182bf9427…7f8db5
Audit this contract →
← previous block·next block →recent activity