← previous blocknext block →recent activity
Analyzing
Block #73,798,547
30 transactions · 24 stateful · 2026-05-11 02:33:28 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.43
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,798,547 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w07w18w09w110w211w319w124w425w526w627w728w829w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x37ed0601…19f5
0x34b655…2a6f
12 touches
15 conflicts
0xd49762c9…1359
0x34b655…2a6f
10 touches
10 conflicts
0xb378025c…30cf
0x34b655…2a6f
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
8 touches
6 conflicts
0xedb848fe…6534
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 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity