← previous blocknext block →recent activity
Analyzing
Block #73,751,151
41 transactions · 32 stateful · 2026-05-10 21:13:41 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
1.61
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #73,751,151 · 41 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w18w09w110w211w312w413w514w635w637w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x4d87512b…897c
0x065c9d…c394
10 touches
10 conflicts
0x99120c08…ee84
0x34b655…2a6f
8 touches
6 conflicts
0x220f4f84…15f8
0x34b655…2a6f
8 touches
6 conflicts
0x8a2657f5…e008
0x34b655…2a6f
8 touches
6 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: Perpl
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity