pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,649,675
26 transactions · 22 stateful · 2026-05-10 09:49:02 UTC
Parallelism
65/100
Blocked
64%
Avg conflicts / tx
1.85
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,649,675 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w09w113w114w215w316w117w218w319w420w521w622w723w825w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x7f81fb82…633e
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0xb159af88…a9e7
0x065c9d…c394
10 touches
10 conflicts
0x15d039e7…4bb6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x543dc30d…2a82
0x34b655…2a6f
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: 0x065c9d28…a9c394
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity