pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,417,349
13 transactions · 12 stateful · 2026-04-30 01:52:26 UTC
Parallelism
39/100
Blocked
58%
Avg conflicts / tx
2.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #71,417,349 · 13 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaadf42dc…f433
0x3bd359…433a
16 touches
28 conflicts
0x00000000…0000
0x7d0364…a52b
16 touches
28 conflicts
0x00000000…0001
0x7d0364…a52b
16 touches
28 conflicts
0x131ec7f4…baaf
0xaca864…7777
16 touches
28 conflicts
0x44ad89ba…cf83
0xaca864…7777
16 touches
28 conflicts
0xa472d565…9fe4
0x3bd359…433a
16 touches
28 conflicts
0xc620b95b…fdd8
0x065c9d…c394
2 touches
0 conflicts
0x037849a8…fa88
0x34b655…2a6f
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: 0x3bd359c1…15433a
28 conflicts on slot 0xaadf42dc0a…d4f433
Audit this contract →
← previous block·next block →recent activity