pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,200,910
14 transactions · 12 stateful · 2026-05-08 08:01:26 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,200,910 · 14 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
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e5ebbf7…ae70
0xc8689a…ee79
4 touches
1 conflict
0x1a4b4152…0a08
0x6ca43f…c331
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x6ca43f…c331
4 touches
1 conflict
0x5b3dfef8…a676
0x6ca43f…c331
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2a354a63…0515
0x065c9d…c394
4 touches
1 conflict
0x962b395a…dd37
0x065c9d…c394
4 touches
1 conflict
0xecca5c61…3688
0x065c9d…c394
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: 0xc8689a47…62ee79
1 conflict on slot 0x4e5ebbf7fb…3fae70
Audit this contract →
← previous block·next block →recent activity